Closed JesMat closed 1 year ago
@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. Can you please elaborate bit more about your integration, Java version and Servlet container version where you are deploying?
For SLF4j binding issue, please refer : https://www.slf4j.org/codes.html#StaticLoggerBinder . I hope that will help. Thanks
@aaron-kumar , Hello and thank you for the response Aaron,
It seems I forgot to mention that we also use your oxalis-as4 plugin. Sorry about that.
I tried to deploy Oxalis without the AS4 plugin: this resulted in no such errors. It seems to only occur when oxalis-as4 is used.
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 Jesper Mathiesen
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.
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: