Hi,
I am currently tinkering with upgrading an existing system to use EJB3 so we can take
advantage of the new interceptors in EJB 3.
The code which currently exists uses a remote session facade which then delegates off to
local session(s) for doing the work. Our first task is to replace the remote facades with
EJB 3 versions and then slowly replace the local sessions on a per item basis. This means
we can leverage the interceptors to bring in the extra functionality required without the
big bang of migrating all the session beans.
However, we have successfully packaged up the facades as EJB 3 and split these into their
own jar still with in the same EAR. But when we try to perform the lookup to get the local
session bean as outlined on
http://blogs.sun.com/enterprisetechtips/entry/ejb_3_0_compatibility_and. This fails but if
we try to connect to them remotely instead of locally then this works.
Is it not possible to use the local 2.X beans with a EJB 3 bean?
Many thanks,
Shane Preater
www.onevisionsupport.com
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098248#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...