Replies: 4 comments
-
@JesMat Sorry, I am unable to reproduce reported issue. i.e. In my case, oxalis war deployed successfully in Servlet container (i.e. Tomcat 9.x) and I am using Java 8. I can see logs being generated. For SLF4j binding issue, please refer : https://www.slf4j.org/codes.html#StaticLoggerBinder . I hope that will help. Thanks |
Beta Was this translation helpful? Give feedback.
-
@aaron-kumar , It seems I forgot to mention that we also use your oxalis-as4 plugin. I tried to deploy Oxalis without the AS4 plugin: this resulted in no such errors. Oxalis v5.3.0 in combination with Oxalis-AS4 v5.3.0 works fine. We are also using Java 8 and Tomcat v9.0.8. Please let me know if I can provide you with any more helpful info! Best regards |
Beta Was this translation helpful? Give feedback.
-
Hi Jesper / @JesMat I hope you are using Oxalis-AS4 version v5.4.0 with Oxalis v5.4.0 If that is the case and you still getting issue then I want to understand your Oxalis-AS4 plugin integration to guide you further. Do you have other things in classpath which is creating problem? |
Beta Was this translation helpful? Give feedback.
-
Hi Jesper, One additional Oxalis user (Member of QA team) confirm that he was Not able to reproduce Logger casting exception with Oxalis-AS4 version v5.4.0 with Oxalis v5.4.0, so it seems that it is your integration specific error. Meanwhile I am converting this issue to discussion since it is Not a bug in release. We can continue discussion there. |
Beta Was this translation helpful? Give feedback.
-
Hello,
We recently attempted an upgrade to version 5.4.0 of oxalis.war, using oxalis.inbound.
The application fails on startup with the error "Error injecting method, java.lang.ClassCastException: org.slf4j.helpers.NOPLoggerFactory cannot be cast to ch.qos.logback.classic.LoggerContext".
Version 5.3.0 works without issues however.
Full stacktrace:
Beta Was this translation helpful? Give feedback.
All reactions