+1 That said i'd use wicket cdi instead of an ejb integration
Wdyt? Le 24 déc. 2012 22:22, "John D. Ament" <[email protected]> a écrit : > EJB 3.1 introduced standardized naming conventions. The best one to use is > the one that matches: > > java:global[/<application-name>]/<module-name>/<bean-name>#<interface-name> > > > On Mon, Dec 24, 2012 at 3:15 PM, Ron Smits <[email protected]> wrote: > > > Evening > > > > Been playing with tomee and wicket. I had quite a hard time getting > wicket > > to play nice with EJB's because it could not use the right naming > strategy. > > Apparently tomee publishes EJB's with two names: > > -- > > HelloEJB!ejb.HelloEJB > > org.apache.openejb.core.ivm.naming.BusinessLocalBeanReference > > HelloEJB org.apache.openejb.core.ivm.naming.BusinessLocalBeanReference > > > > they are available from "java:global/tomee" context where tomee is the > name > > of the project I am working on. there is an easy solution for with the > > wicket javaee-inject module. but what would be the best jndi name to use? > > My 'guess' would be the first one as it is likely to be more unique. > > > > comments? > > > > Ron > > I Haven't Lost My Mind - It's Backed Up On Disk Somewhere > > >
