You beat me to this before I could ping you on it :) bstansberry(a)jboss.com wrote : As long as @Clustered itself is in ha-client, ClusteredImpl depends on ha-client. So I don't see the benefit of replacing the class with a string. And if ClusteredImpl (to be moved to ejb3-impl) depends on ha-client, ejb3-impl will depend on ha-client. I'd like to avoid this. bstansberry(a)jboss.com wrote : I suppose if you changed it to a string *and* took the annotation itself back into ejb3, then you get a benefit. Yep. Though a couple months back we determined that @Clustered was not specific to EJB3, so we put it into HA. I'd originally put ClusteredImpl in there as well, but took it back when you'd asked. So I see a couple solutions: 1) Move @Clustered to ejb3-ext-api, ClusteredImpl to ejb3-impl, and make Strings out of the load balance configuration. This makes @Clustered EJB3-specific. 2) Put ClusteredImpl back into HA somewhere, with dependency on ha-client to fulfill the reference to LoadBalancePolicy. EJB3 is the only project using this class, but then there'd be no API leak. bstansberry(a)jboss.com wrote : Before going down this road though, we should determine how to handle the aspects module, which also depends on the ha-client project. That necessary, or your preference? :) Thx. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114382#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...