If you do that, I'll bet you'll cause memory leaks due to NonSerializableFactory -> context -> object -> class -> undeployed classloader because some places aren't getting tidied correctly.
I put a TODO in the WebDeployer, because it never gets tidied up (it is left to garbage collection) See AbstractWebDeployer.parseWebAppDescriptors() On Tue, 2005-05-31 at 19:58, Bill Burke wrote: > I guess what I"m saying is, shouldn't NSF be keyed on Context instance > and base String name? > > Bill Burke wrote: > > I'm finding that I want to bind a non-serializable into > > java:comp/EntityManager. The problem is that NonSerializableFactory > > keys on the Name.toString() not on any other type of key so this is not > > viable for things put in java:comp with the same name across EJBs/servlets. -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
