This content has been marked as final.
Show 3 replies
-
1. Re: Custom JNDI bindings without bean interface
wolfc Nov 7, 2011 5:50 AM (in response to akoledzhikov)Can you elaborate on the verbosity of the default names?
beanInterface is mandatory, but can contain the bean class for no-interface views.
@EJB(name = "java:global/ejb/AlienEntityHome", beanInterface = AlienEntityHome.class) @LocalBean // needed if implementing any interfaces
-
2. Re: Custom JNDI bindings without bean interface
akoledzhikov Nov 8, 2011 8:01 AM (in response to wolfc)Well, the new portable jndi name syntax is quite long - .../<archive-name>/<module-name>/BeanClassName, and may confuse someone who does not know what's in those archives. /aliens/AlienEntityHome is much clearer and developer-friendly in my opinion.
Using the class as a beanInterface worked for me, thanks!
-
3. Re: Custom JNDI bindings without bean interface
wolfc Nov 8, 2011 9:55 AM (in response to akoledzhikov)Kudos for finding such a solution.