Re: [webbeans-dev] Spec Conflicts Between JSR-299, JSR-318
On Wed, Mar 18, 2009 at 1:11 AM, Andrew Lee Rubinger <alr(a)jboss.org> wrote:
* JSR-299 implementations are treated the same as any client of EJB;
they use/consume EJB as one of the target component models.
That is no longer true, since the pluggability contracts have been removed.
EJB and 299 are just aspects of the EE container.
* A mechanism EJB makes available to JSR-299 should be available to
everyone.
I don't see why this should necessarily by the case. 299 is a piece of
the container.
1) EJB does not define an endpoint for SFSB removal outside
business/component method @Remove/remove() and timeout
But 299 does. What's the problem?
2) JSR-299 defines activity in the middle of EJB Lifecycle
JSR-299 PR2 6.11 - "When the EJB container creates a new instance of an EJB,
the container must perform the following steps after Java EE injection has
been performed and before the @PostConstruct callback occurs..."
EJB defines no callback mechanism for a hypothetical @PostInstanciated
before @PostConstruct. Thus there's no hook defined for WB to do its magic.
299 is now part of the container. It doesn't need a hook.
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org