[jboss-dev-forums] [JBoss AS Development] - Re: Naming over Remoting 3

[ron.sigal@jboss.com]

Hey A,

Hope I'm not being too familiar, addressing you by your first initial.  :)

I've been playing around with combining invokablecontainer and proxies, and I have a problem.  

If I redefine Interceptor.invoke() to accept an org.jboss.invokable.container.api.Invocation instead of an org.jboss.invocation.Invocation, if I adjust ClientContainer to hold an org.jboss.invokable.container.api.InvocationContext instead of an org.jboss.invocation.InvocationContext, and if I redefine ClientContainer.invoke() to create an org.jboss.invokable.container.core.InvocationImpl instead of an org.jboss.invocation.Invocation, then I have a problem injecting the ClientContainer's InvocationContext into the Invocation.  I wanted to use the constructor 


  | InvocationImpl(final Method targetMethod, final Object[] args, final InvocationContextProvider context)
  | 

but it's a package-whatever.  And if I call Invocation.getContext() to populate it with ClientContainer's InvocationContext, I can't really do much because InvocationContext doesn't have an iterator, just 


  | Object getProperty(Object key) throws IllegalArgumentException;
  | 

which doesn't help if I don't know what's in the InvocationContext.

Am I just trying to do something that doesn't make sense?  Otherwise, what do you think of adding an iterator to InvocationContext?

-Ron (you can call me R)

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

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