Yes. Having one object init another which inits a new instance of the first would obviously never work. This application, however, has been working for over a year now.
My assumption is that the circular referencing problem can be avoided with EJBs (and must have been with previous versions of JBoss) because, using the previous example, the local (proxy) ref being requested by BeanC would NOT require a NEW instance of BeanA, so BeanA's ejbCreate would not be called again (these are stateless session beans). I was just wondering if the way the container pools stateless session beans changed, and/or whether there is a configuration change that I can make to avoid this. Thanks again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877069#3877069 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877069 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
