[
https://jira.jboss.org/browse/JBAS-8290?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated JBAS-8290:
----------------------------
Summary: Implement solid SessionObjectReference (was: Implement solid isRemoved()
method for SessionObjectReference)
Assignee: Marius Bogoevici
Priority: Critical (was: Major)
Description:
JBossSessionObjectReference is a bit hacky right now:
1) Needs a proper implementation of isRemoved which interrogates the EJB container to
determine the state of the reference
2) Needs a Remove implementation that can cope with no-interface-view beans
3) Needs to lookup the actual reference for getBusinessObject() not just cast the local
proxy. Note that we may request remote EJBs through this mechanism!
was:Currently we don't actually detect if the user or EJB container removes the EJB,
not WB
Implement solid SessionObjectReference
--------------------------------------
Key: JBAS-8290
URL:
https://jira.jboss.org/browse/JBAS-8290
Project: JBoss Application Server
Issue Type: Bug
Components: Weld/CDI
Reporter: Pete Muir
Assignee: Marius Bogoevici
Priority: Critical
Fix For: 6.0.0.CR1
JBossSessionObjectReference is a bit hacky right now:
1) Needs a proper implementation of isRemoved which interrogates the EJB container to
determine the state of the reference
2) Needs a Remove implementation that can cope with no-interface-view beans
3) Needs to lookup the actual reference for getBusinessObject() not just cast the local
proxy. Note that we may request remote EJBs through this mechanism!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira