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

[scott.stark@jboss.org]

"Carlo" wrote : 
  | Whether it will be ATTCTMVP (tm) or something else ( for example 
  | http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/remoting2/src/main/java/org/jboss/ejb3/remoting/endpoint/RemotableEndpoint.java 
  | ) remains to be seen. I like 
  | http://anonsvn.jboss.org/repos/common/invokablecontainer/trunk/api/src/main/java/org/jboss/ejb3/container/api/Invocation.java 
  | with the exception that target is not a first class citizen.
  | 
  | AOPRemotingInvocationHandler & Dispatcher definitely need to go. The 
  | first, because remoting is not an aspect, the second because it's a 
  | singleton with weird SPI ( 
  | http://fisheye.jboss.org/browse/JBossAS/trunk/ejb3/src/main/org/jboss/ejb3/session/ClassProxyHack.java?r=69926 
  | ).
  | 
  | Now if you put JNDI, Remoting and proxies in one sentence one 
  | requirement is the most important:
  | - all proxies must be transport unaware.
  | 
  | So if I bind an EJB into JNDI it doesn't matter whether I lookup through 
  | an HTTP(S), IIOP or whatever to get a proxy tied to the connection with 
  | which I'm communicating with AS.
  | The same goes for clustering, that is just a virtual connection to a 
  | virtual host (/ real cluster).
  | 


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

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