[jboss-dev-forums] [Design of EJB 3.0] - Delegating all invocations to ejb3-interceptors AbstractCont

[wolfc]

For some methods on EJBContext we need to know the invocation context in which we're invoked to actually allow or disallow a request. Right now we analyse not the invocation context, but the security context or transaction context and give the real answer back.

For example setRollbackOnly in @PostConstruct on a SFSB runs within the transaction context of the caller,  so it works correctly.
But the spec defines the transaction context of a lifecycle callback as being unknown, thus it's actually not allowed.

So what if we delegate all invocations to ejb3-interceptors AbstractContainer (including the actual injection (instead of field.set etc))?
Then ejb3-interceptors always knows the current invocation context.
This also means we don't set the current invocation interceptor anymore in aop.xml.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167580#4167580

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167580