Hi, re: http://jira.jboss.com/jira/browse/JBAS-5647 Taking in account that this JIRA requires an API change, I'd like to get it done asap. Creating the response filter for HA-JNDI and making HA-JNDI use this new API can come a bit later. At the JGroups level, the API that we need to call to pass the RspFilter is: public RspList callRemoteMethods(Vector dests, MethodCall method_call, int mode, long timeout, | boolean use_anycasting, boolean oob, RspFilter filter) At the HAPartition level, we can either change callMethodOnCluster, or overload it to add, at least, RspFilter. Overloading is probably safer from a backwards compatibility perspective. This is for AS 5.0.0.GA, so I guess backwards compatibility is not a top priority. I'm easy with either. The second thing to decide is what to do about the extra parameters that callRemoteMethods takes which are: boolean use_anycasting, boolean oob Do we wanna expose them to HAPartition clients? In the case of anycast, I think this would only make sense if the destination members where exposed in the HAPartition API, otherwise, to the HAPartition client, it's as if it was calling the method to all members in the cluster. Anycast only makes sense when you're calling on a subset of the cluster. In the case of oob, messages sent like this are used for non-application usages such as FD heartbeats (see http://jira.jboss.com/jira/browse/JGRP-205), so I'd leave it out again. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163149#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...