"Johnson, Lance" wrote: > We are in the process of developing an ejb that is a corba client. One of > the drawbacks that I have seen so far is that when our EJB is passivated we > must disconnect all CORBA connections. If we don't do this, I think, we > will have CORBA object leaks in our jacOrb code. Then, when it is activated > we have to reconnect to our servers (as needed).
it is exactly what I 'm doing too ... > Is there a way to get around this overhead of disconnecting and > reconnecting? Can you turn off passivating and activating on the container? it seems to me a bad idea to do it (seems to brake the idea behind the EJB stuff) but I remenber to have seen some parameters for the cache ... so I conclude that you too create your 'corba' ejb as 'session bean', I was wondering if 'pure' ejb-proxy for corba service (*) should not be seen as sometime as 'entity'(bean managed) or even stateless ejb ? Finally what about an ejb which is a corba server, somebody tried that ? jc (*) I mean ejb which enable to reach all corba services by forwarding the call withou adding 'intelligence' _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
