"bstansberry(a)jboss.com" wrote :
| Yes, that's the concept I mean. JBoss AS has traditionally put the server in
charge of determining the behavior and initial state of proxies, because the server has
more information (complex configs, runtime state of the server/cluster etc).
|
Ok, I'll do over. Maybe I'll adapt RemotingProxyFactory, the version of
JRMPProxyFactory I created for JBAS-4456 "Replace JRMPProxyService with a remoting
based bean", to work with Remoting 3. RemotingProxyFactory lives in jboss-aspects,
since there didn't seem to be any better place to put it, but maybe it could go in
invokablecontainer.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267178#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...