Andrew, I'm done with the changes including the review comments. I am planning to summarize the exact changes and even upload the new patch to the JIRA in my next post. Brian, As discussed in this thread, &quot;bstansberry(a)jboss.com&quot; wrote : | | If you refresh your ejb3 checkout, you'll find that there is a new ejb3 module added -- proxy-clustered. The classes in this module are mostly extensions of the ones in proxy that add the behavior necessary for cluster-aware proxies. | | Since these classes are extensions, there's a fair amount of overriding of protected methods, including some methods you're probably changing (e.g. JndiSessionRegistrarBase.createJndiReferenceBindingSet(...)). So, you're patch will need to include changes to proxy-clustered as well. AIUI, you're mostly working on passing an InvokableContext param instead of a bunch of details. The changes to proxy-clustered needed to handle that should be simple and pretty obvious. i have taken care of the necessary changes to the classes in proxy-clustered module. However, i see that the pom of proxy-clustered has a dependency on 0.1.2 version of proxy module: | <dependency> | <groupId>org.jboss.ejb3</groupId> | <artifactId>jboss-ejb3-proxy</artifactId> | <version>0.1.2</version> | </dependency> Is there any specific reason for this dependency? For integrating the changes in the proxy module with the proxy-clustered module, i would have to use a higher version of ejb3-proxy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177800#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...