I also think this is something that maybe just been highlighted by a classloader issue somewhere else. Has anything been changed with class loading over the weekend? Also can't see anything specific but gut tells me this is not as simple as it looks.
The following log entries are of concern: SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/d:/OrproVisionServer/openejb/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/D:/OrproVisionServer/openejb/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class] I am filtering out the duplicates as discussed and OpenEJB is happy - no more duplicate deployment id's etc. But, multiple SLF4J bindings in on the same path usually boil down to a classloader issue? -- View this message in context: http://openejb.979440.n4.nabble.com/Trunk-classloading-is-broken-with-case-sensitive-paths-tp4344116p4345206.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
