Good question indeed. I'd say that even without a JSR we can already discuss our wishlists, can't we? My nr 1 item; further or even totally integrate with CDI ;) Kind regards, Arjan

Hi, Not at the moment, but pieces of work for it have been done (PRs pending) and I hope to be able to work on that ASAP, so should be sooner rather than later. Kind regards, Arjan Tijms

Hi, It's indeed a tad too late if the Proposed Final Draft is only days away. Perhaps in the meantime individual application servers can do a little bit more to integrate with CDI out of the box, like

Hi, Because it's another Java EE spec that had its own DI engine and gave it up for the platform one. I'm really not sure why the REST API of Java EE should have its own DI engine. Does Spring MVC als

Can you give me any good reason why we should keep @ManagedBean? It has been deprecated already and everything in and around it has been superseded by CDI. Also remember that pruning is a multi releas

Hi, IMHO it would be best to just commit and make CDI mandatory. This is exactly what we've been in doing in JSF as well. There's a transition period, sure, but in the end things should be a lot bette

Hi, While I agree this is not ideal, it's certainly not unprecedented in Java EE. More than a few specs depend on such integration code, typically via a product specific SPI that the application serve

Hi, Thanks for your reply, I see your point although I have a slightly different vision. But for now, let's table that sub-discussion ;) As for top CDI support or even (in time) fully depending on CDI

Sergey, I think what you're saying here is that because some users think Java EE is not good, we as Java EE people should partially abandon it instead of making it better? Maybe the entire reason that

Why?

Yes. It's another injection and bean model and doesn't play nice with the platform wide services for things such as extensions, decorators and interceptors. This is also why we deprecated and native m

Hi, It's not just another EE spec, but one of the fundamental EE specs. IMHO; open as possible also means that you eventually commit to nothing and only make it more difficult and confusing to use in

Hi, I too would greatly love to see this happening. CDI alignment IMHO should have been -the- major theme of Java EE and unfortunately too few steps have been made towards that goal. Kind regards, Arj