You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2007/03/15 22:14:09 UTC
[jira] Closed: (OPENEJB-543) InvocationContext
[ https://issues.apache.org/jira/browse/OPENEJB-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-543.
---------------------------------
Resolution: Fixed
> InvocationContext
> -----------------
>
> Key: OPENEJB-543
> URL: https://issues.apache.org/jira/browse/OPENEJB-543
> Project: OpenEJB
> Issue Type: Sub-task
> Components: ejb3 simplified
> Affects Versions: 3.0
> Reporter: David Blevins
> Assigned To: Dain Sundstrom
> Fix For: 3.0
>
>
> Implement an InvocationContext for interceptor chain. The rule with all standard interface implementations is to not expose any additional methods; this may require a wrapper implementation that delegates to a fully functional implementation.
> package javax.ejb;
> public interface InvocationContext {
> public Object getBean();
> public Method getMethod();
> public Object[] getParameters();
> public void setParameters(Object[] parameters);
> public java.util.Map getContextData();
> public Object proceed() throws Exception;
> }
> note: getMethod returns null for lifecycle callbacks
> note: proceed returns null for void methods
> note: context data lives only for one chain invocation
> question: how many times can proceed be called by an interceptor?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.