Closed glassfishrobot closed 11 years ago
Reported by mvatkina
@arjantijms said: Perhaps also clarify how this happens? In practice some users are confused by this, see e.g. http://stackoverflow.com/questions/10403531/how-does-cdi-remove-stateful-session-bean
petermuir said: Arjan, I suspect that this clarification is better off in the CDI spec, can you file a http://issues.jboss.org/browse/CDI issue for me, and I can work out how to clarify this is not done via a standard API.
@arjantijms said: Peter, I've created the issue here: https://issues.jboss.org/browse/CDI-273 Thanks in advance for looking at this.
Wouldn't it eventually be more convenient if EJB did have a standard API for this? With such API a CDI implementation may be more easily portable to different application servers.
petermuir said: It would be better for EJB to have an API for this, but it is only one small part of the vendor specific integration between a CDI container and an EJB container. Getting the integration fully pluggable would be quite a lot of work.
mvatkina said: For EJB to define an API on how to integrate with it, is a substantial task. But if CDI defines the API of its integration into other containers, it will reduce duplication of this requirement across all containers that it integrates with (and scales better).
mvatkina said: Changed the note that a container can also invoke the PreDestroymethod on the instance without a client call to remove the session object to include the case of when the context to which the CDI-enabled bean instance belongs to is destroyed
wolfc said: Note to self, we already have a similar API for that called a Home Interface View.
For future we might consider adding such a facility to an EJB 3 bean.
Was assigned to mvatkina
This issue was imported from java.net JIRA EJB_SPEC-63
Marked as fixed on Thursday, November 29th 2012, 6:26:44 pm
SFSB can be removed by CDI destroy() invocation
Affected Versions
[3.2]