As the guy who worked heavily to put this in based on an OpenEJB feature, it's heavily used in our camp.
It does seem however, that at the spec level we've been slowly backing away from it due to pressure from vendors who don't want to support it; having been downgraded from required to optional.
Rather than removing it as our very first act as an open community, I'd personally prefer to spend a spec cycle seeing how well supported it is and if there aren't things that can be addressed to make it more desirable to implement.
Being perfectly honest, this feature is Spring Boot before there was a Spring Boot. Our mistake was not going full tilt and pushing this at a platform level. If we had, we'd have dominated the Uber Jar space back in 2009.
-- David Blevins 310-633-3852
Hi,This idea came
up during our IBM discussions relating to the Pruning Vote that Steve initiated.
What about the EJB Embeddable Container? We provide one because
the Spec requires it, but we have no customers using it (that we know of
anyway). Is the pruning of the EJB Embeddable Container something
we could also put out for a Vote? Or, is our customer usage an anomaly
and there is industry interest in this artifact? Thanks! --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________ jakartaee-platform-dev mailing list jakartaee-platform-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
|