I use it! I recently switched from Glassfish to TomEE and didn't have to
change any JNDI lookup worked as they were. Of course, I only used the
portable JNDI names.
However, I'm considering changing to CDI for the injection part only.
EJBs still offer very interesting features like transactions and timers.
I found this interesting article discussing how to combine CDI and EJB :
http://www.oracle.com/technetwork/articles/java/ejb-3-1-175064.html
Bertrand
On 12/10/2012 6:49 AM, Martin Grigorov wrote:
Hi,
For me it is like the Portlet integration - none of the active devs
uses it and it will be hard to maintain it.
Not sure how many users use it actually. Recently there were few
questions about it but that's all.
Last time when I used Java EE application server (somewhere around
2007) I noticed that JNDI names are not very consistent across Java EE
implementations, i.e. this is not very portable and users will
complain why it doesn't work for their WebSphere, for example.
Also I'm not sure about the future of EJB since there is CDI.
On Fri, Oct 12, 2012 at 1:39 PM, Andrea Del Bene <[email protected]> wrote:
Hi,
is there any plan or any will to integrate JavaEEComponentInjector into
Wicket distribution? At the moment this listener is included into
WicketStuff project.
