[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: ProfileService shutdown and undeploy order

[adrian@jboss.org]

"bstansberry at jboss.com" wrote : 
  | BTW, IIRC the failure message has changed; used to mention org.jboss.iiop.naming.ORBInitialContextFactory, perhaps as a CNFE. Wouldn't surprise me if solving the current error condition just brings that one back.

Yes, the way it was working, it couldn't see conf/jndi.properties either.

When the latest MC code gets into trunk,
your stop() will be invoked with the context classloader of your deploy/cluster
deployment so all this hacking around with the context classloader in the profile service
will go away.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123646#4123646

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123646