As i answered to the other mail. I'm not sure. Based on the code i
started with i thought i would have to take care of the instances (and
therefore only hold one for a stateless bean).
I'm not that familiar with EJB injection and lookups. but when i think
about it JNDI has to hold the one instance so it shouldnt matter.
but i'm not sure.
Greetings
Alexander
Jeromy Evans schrieb:
Alexander Baetz wrote:
Hi,
i'm currently working on a new Interceptor for EJB Injection on
Actions. I allready extendet it to work on fields and methods. But
since i dont like to make my own Annotation type i wanted to use the
javax.ejb.ejb anotation. But there is a small problem with that:
the annotation used by the ejb3-plugin for struts 2 has a field that
determines if the bean is statefull or stateless. I don't have this
bean, so how do i determine for the injection if the bean is statefull?
I'm not familiar with the plugin, but why does it need to know whether
the bean is statefull or stateless? I don't think that should affect
the lookup or injection into the action, should it? Only the
Container that instantiates the bean and provides the instance cares,
doesn't it?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]