On Mar 11, 3:42 pm, Gianluigi <[email protected]> wrote: > >...if you don't want to bind different EJB3TestRemotes to different > >names. > > not different names, different IMPLEMENTATIONS. The @Names annotation is a > selector to choose with concrete implementation of the local/remote ebj > interface inject (and u can use another annotation if u prefer)
That's what I wanted to say with this - Or to be even more exact: Binding EJBTestRemotes annotated with different @Named values to different provider implementations :-)) > > >I haven't tried this though - I'm simply using the @EJB annotation to > >inject EJBs in GlassFish. > > Yep, but with @EJB you cannot inject your EJB3 into a non managed object. You > have to use the ejb3 into servlet or other ejb3 NOT into a POJO. That's true of course. It's just, that I haven't needed it so far. Maybe it's worth noting, that there's also an alternative: CDI (aka "Web Beans", JSR-330), which can bind EJBs natively. That said, I generally prefer Guice, and I like the fact that you've written an article about integrating EJBs with Guice. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
