A callback on EJB removal

[pmuir]

I need to have a callback from the EJB container when an EJB is removed for some reason. The JSR-299 spec requires us to ignore any EJBs that have been removed, so I need to mark an instance ignored.

https://jira.jboss.org/jira/browse/WBRI-165

Again, not sure of the best API for this, so open to suggestions...

[alrubinger]

Just for SFSB I'd imagine?

Our standard M.O. applies I guess; make some SPI to register a callback listener in wb-as-int and we'll invoke upon it via some EJB3 optional add-on component.

What contextual information do you need? Session ID?

S,
ALR

[pmuir]

"ALRubinger" wrote:
Just for SFSB I'd imagine?

Oops, yes :-)

Our standard M.O. applies I guess; make some SPI to register a callback listener in wb-as-int and we'll invoke upon it via some EJB3 optional add-on component.

What contextual information do you need? Session ID?

What is the best way (that ideally is standard, otherwise we'll need another SPI for identifying an SFSB) to identify an SFSB instance?

I was struggling with this, as the object instance we obtained from JNDI isn't useful. I guess we could use the object instance obtained from invocationContext.getTarget()...

[pmuir]

N.B. This is effectively the inverse of http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151896, where, rather than wanting to be notified that an EJB was removed by someone other than Web Beans, we want to request an EJB be removed.

[alrubinger]

What is the best way (that ideally is standard, otherwise we'll need another SPI for identifying an SFSB) to identify an SFSB instance?

You mean the ID of a given proxy? ATM we'd be diving into implementation details by getting the it out of a field in the InvocationHandler.

http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/proxy/src/main/java/org/jboss/ejb3/proxy/handler/session/stateful/StatefulProxyInvocationHandlerBase.java

You can't rely upon that now by doing Proxy.getInvocationHandler(proxy) because that's digging too deep into internals.

We could expose this by adding interface support for a JBossStatefulSessionObject in the proxy, which has some method getId():

JBossStatefulSessionObject proxy = (JBossStatefulSessionObject)jndiContext.lookup("address");
Serializable id = proxy.getId();

WDYT?

S,
ALR

[wolfc]

Why doesn't the @PreDestroy on the SeamInterceptor work?

[alrubinger]

"ALRubinger" wrote:
We could expose this by adding interface support for a JBossStatefulSessionObject in the proxy, which has some method getId();

I did this in r85648 for https://jira.jboss.org/jira/browse/EJBTHREE-1758.

StatefulSessionProxy statefulProxy = (StatefulSessionProxy)proxy;
Serializable sessionId = statefulProxy.getSessionId();

S,
ALR

[pmuir]

"wolfc" wrote:
Why doesn't the @PreDestroy on the SeamInterceptor work?

It probably does, I hadn't thought of this. I'll check it out.

[pmuir]

This works well - thanks Carlo for pointing out the obvious :-)