[EMAIL PROTECTED] wrote : For stateful beans they are very different.
Gavin, can you explain more precissely which is the difference with stateful
beans between @In and @EJB, because I need to choose the correct annotation if
they behave different.
Regards
Sebastian
View the original post :
So, in case of a stateless Bean Seam uses for Injection via @In a common
JNDI-lookup to the containers registry(ENC) ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3956544#3956544
Reply to the post :
@EJB is EJB injection. For a stateful bean, you will get a new instance
created when your other been is created. Think of it as a private instance
that Seam knows nothing about - nobody else can inject that instance. For
stateful components, you are more likely to want instances to live in
bambata wrote : So, in case of a stateless Bean Seam uses for Injection via
@In a common
| JNDI-lookup to the containers registry(ENC) ?
|
|
In the case of a SLSB, @In does a JNDI lookup (global or ENC). In the case of a
JavaBean, it does a new.
View the original post :
Right, @In is handled by Seam, and is aware of the Seam names and Seam
contexts. For stateless beans there is not really a whole lot of difference
between the two. In that case, they are each just sugar over a JNDI lookup. For
stateful beans they are very different.
View the original post :
