|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Since this bug was opened I've started to port an application to run in websphere 7.
All the jars kept out of the ear and war and are configured separately. We are also using spring schedule tasks, but they don't run before the servlets. How does that happen and why does that cause a class loader issue?
Logback works fine for me. At lest it finds the logback.xml ok. I'm not sure how I'm going to override it but that is a separate matter.
So can you explain your classloader setup more precisely?