With the effort underway to consolidate the client side interceptor models (see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970879#...), need to revisit a bit the LoadBalancePolicy interface. We'd decided earlier to create a simple base interface with only chooseTarget(FamilyClusterInfo fci) and then to leave a legacy subinterface with a method that took o.j.invocation.Invocation as a param. If we're going to consolidate to a single interceptor model, this raises a few questions: 1) Will we get rid of the subinterface w/ o.j.invocation.Invocation? (An indirect way of asking whether we'll get rid of the old interceptor model for 5.0, or leave it around for ease of migration.) 2) Will we want a method chooseTarget(FamilyClusterInfo, o.j.aop.joinpoint.Invocation) ? This will provide an API similar to the old detached invoker model that any custom policies that people wrote can adapt to. 3) If yes to #1 and #2, in the base interface or a subinterface? 4) Another possibility Tom and I discussed is to create an abstraction of the data that would be passed in the Invocation and pass that to the LoadBalancePolicy, thus reducing the coupling to the invocation type. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971120#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...