Yes, @EJB is still available, and it is still required in some cases. But the general approach to injection has changed with CDI. See http://seamframework.org/Community/InjectingWithEJBOrInject for a discussion.
My original question is about how to use Wicket with CDI (injecting EJBs and other beans), and your suggestion is not to use CDI, which does not really solve the problem... By the way, the nice thing about @Inject is that you no longer have to use JNDI lookups or bean names in @EJB annotations. And the specific problem is NOT that @Inject does not not work for EJBs, but the injected proxies fail to serialize properly. If I understand the javaee-inject implementation correctly, it takes care not to serialize proxies but replaces them by references on serialization, looking up the same reference again on deserialization. I suppose my problem would be solved if the CDI InjectionTarget were using this approach, but this is a CDI implementation detail and out of my control. Anybody else out there using Wicket+CDI+EJB? Have you come across similar problems? Best regards, Harald -----Ursprüngliche Nachricht----- Von: Major Péter [mailto:majorpe...@sch.bme.hu] Gesendet: Mittwoch, 7. Juli 2010 19:43 An: users@wicket.apache.org Betreff: Re: AW: Serialization of injected EJBs Nope, it does not support CDI. AFAIK @EJB is not deprecated or old-style, and it's still available in Java EE 6. The thread was about injecting EJB's and JavaEE Inject does exactly that. You can always use lookups for your beans/CDI stuff... Regards, Peter 2010-07-07 19:34 keltezéssel, Harald Wellmann írta: > Does javaee-inject support CDI at all? I cannot find any @Inject annotations > in the examples you mentioned, they all seem to be in Java EE 5 style, not > Java EE 6. > > Regards, > > Harald --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
