Eric
today I noticed that there is an issue with the changes to the classpath
in the wrapper.conf.
You removed the classpath-entries for:
wrapper.java.classpath.10=webapp/WEB-INF/lib
wrapper.java.classpath.11=webapp/WEB-INF/lib/*.jar
This was done intentionally, as the WAR should not expect anything to be
loaded from the classpath, but get everything it needs from the WAR
classloader.
But the service wrapper tries to instantiate the classes referenced in
the log4j.properties.
So it at least depends on wso2utils-1.2.jar and all its dependencies.
Adding back the above two lines fixed that issue for me.
Can you check the latest ESB 1.7 branch (with Synapse 1.2).. I couldn't
reproduce this at all.. when starting the embedded Tomcat, we provide a
dummy log4j.properties for it to initialize, and that does not refer to
any other classes
asankha
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
