if you are creating an interceptor within a ejb3 application i really reccomend
that you use the ejb3 interceptors. they are managed by the appserver and are
really easy to set up. - and they are part of the ejb3 spec too.
View the original post :
http://www.jboss.com/index.html?module=bb&op=vi
I'm not sure what you mean, but the aop interceptors are not part of the bean's
ENC, so you need to use the global JNDI name of the bean
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984988#3984988
Reply to the post :
http://www.jboss.com/index.html?module=
Hi, I'm now usign this code:
| context = new InitialContext();
| System.out.println(" my context name is" + context.getNameInNamespace());
| login = (LoginAction) context.lookup("...my jndi string");
|
|
...but the name is empty !! and the lookup throws exception !
View the orig
You would have to use InitialContext() and lookup() @EJB is only recognised by
jee 5 managed artifacts.
However, you could use an EJB 3 interceptor.
http://docs.jboss.org/ejb3/app-server/tutorial/index.html (See the Interceptors
section). This also comes with the ejb 3 download w/ runnable exam
