Kevan, Do you see anything wrong with the in-place deployment? Is this an issue with openejb not setting the classloader?
jklcom99 wrote: > > Yes, I did and it ran. > > The difference I see in the ear deployed structure is that your MDB is in > WEB-INF->lib > > Whereas we are doing an in-place deployment with the following deployed > structure. All MDB's along with other classes are available in the lib > folder. The manifest classpath of app-ejb-jar has references to the > required MDB's via ../lib/myApp.jar. This worked under G1.1.1 > > deployed > apps > myApp.ear > myWeb.war > lib > META-INF > app-ejb.jar > META-INF > app-ejb-jar.xml > MANIFEST.MF > app-openejb-jar.xml > > Thank you > > > > Kevan Miller wrote: >> >> >> On Sep 17, 2008, at 12:28 AM, jklcom99 wrote: >> >>> >>> I don't have the <module>...</module> in ear deployment plan. It >>> still got >>> the wrong classloader after adding <module>...</module> >> >> Can you (did you) run a test using my test apps? >> >> --kevan >> >> >> > > -- View this message in context: http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p19554557.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
