[jboss-user] [EJB 3.0] - Re: Can SLSB be dirty after new injection?

wolfc do-not-reply at jboss.com
Mon Jul 9 04:37:56 EDT 2007

"gena777" wrote : Couldn't it be better, to purge the dirty SLSB and from some threshold to fill the pool with new instances?
You can create your own interceptor which determines if you use a new instance and when to discard it. See http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/ejb3/src/main/org/jboss/ejb3/stateless/StatelessInstanceInterceptor.java?view=markup

"gena777" wrote : Are there some important reason why the SLSBs aren't one way? Is it really so expensive, to create asynchronously thousands  of whole instances of a bean and put them on demand to the method-ready pool?
Yes and yes. Injection can become quit heavy. But each application is different, you'll have to benchmark when you got your new interceptor up and running.

"gena777" wrote : Isn't the throwing an exception an expensive way to remove the dirty instance?
Yes, if you want open a new feature issue in JIRA. An extension of SessionContext with a setDiscard method might be the solution.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061842#4061842

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061842

More information about the jboss-user mailing list