Oh, well, that is what comments and test cases are for. Add a test case that demonstrates the problem and I'll fix this in the next release.
> Hi, > There is a reason why I did not start the pool from the ContainerFactory > (well another that the classloader issue that you fixed ;) ) > The setSessionContext have, in most cases, Home lookup (to cache them) > and if all beans are not deployed you can have JNDI lookup failure (when > using flat ejb-jar's for example). It is a problem that can happen in > other cases as well I must agree and that the developer should take care > of, but it appears as a "Jboss bug" when you first see it. > I can only see one solution : have a postinit() method in container that > is called when all containers have started. > > Vincent. ----- Original Message ----- From: "Vincent Harcq" <[EMAIL PROTECTED]> To: "'Scott M Stark'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, December 29, 2001 6:15 PM Subject: RE: [JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins AbstractInstancePool.java MessageDrivenInstanceInterceptor.java StatefulSessionInstanceInterceptor.java StatelessSessionInstanceInterceptor.java _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
