anonymous wrote : No, you can configure the EJB container without out the
CachedConnectionInterceptor and tie it to specific EJB where you don't want the
connections to be automatically closed... This is a *HACK* , refractor the LegacyObject as
explained before.
| I am not telling you to play with CachedConnectionManager.
|
It's not named LegacyObject for nothing - if I could refactor it, I would. OK, bad
water here, I'll get out of here and try something else. Thanks for the explanation!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190175#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...