"ron.sigal(a)jboss.com" wrote : "bstansberry(a)jboss.com" wrote : | | Will there be step where the server controls creation of the proxy used for the actual lookup? With what you describe above, the creation of the proxy is completely driven by the client. Which is fine for the initial connection to the server, but removes the ability for the server to customize the proxy. | | | | Actually, the proxy returned by NamingProxyFactory is the proxy that does the actual lookup. Hmmm. Are you referring, perhaps, to using JRMPProxyFactory to add interceptors to a proxy? I didn't think of that, probably since there don't seem to be any actual examples in the out-of-the-box configurations. OK, I'll work on that. 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). HANamingService is an example; it's just that the proxy it creates is mostly statically defined, not defined by some XML configuration or something. It does have dynamic state though (the list of targets). And actually, the behavior of its proxies is somewhat externally configurable - the load balance policy to use is configurable (see all/deploy/cluster/hajndi-jboss-beans.xml, the "loadBalancePolicy" attribute.) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267176#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...