Thanks very much for your support, it works now for me, too. I'd never have guessed that sun-ejb-jar.xml was the problem. Including several proprietary plans is a good pattern to keep an app binary portable, so I think the sun-ejb-jar.xml problem should be fixed.
Thanks, Juergen Ivan Xu wrote: > > Just googled, find a Geronimo JIRA > http://issues.apache.org/jira/browse/GERONIMO-4573 > Not sure why we did not set openejb.vendor.config=GERONIMO in Geronimo by > default, I will add it to the openejb plan file. > > 2009/9/17 Kevan Miller <[email protected]> > >> >> On Sep 17, 2009, at 10:25 AM, Ivan wrote: >> >> Hi >>> After removing the sun-ejb-jar.xml from the ejb jar file, you should >>> deploy the application successfully. By the way, you should also add a >>> resource link for the SOCKET_MDB1. >>> >> >> Thanks Ivan! We've had sun-ejb-jar.xml problems before. Thought it was >> fixed (in Geronimo or OpenEJB?), but maybe there's a problem on 2.2? >> Removing the file, may get Juergen up and running, but there's an >> underlying >> which should be fixed for 2.2. >> >> --kevan >> >> > > > -- > Ivan > > -- View this message in context: http://www.nabble.com/Container-does-not-exist-tp25461869s134p25503971.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
