anonymous wrote : You beat me to this before I could ping you on it :) By luck the JIRA message was prominent in my morning e-mail pile, so you got a response before the deluge buried me. :-) anonymous wrote : | 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. Yeah, but then Adrian kindly discovered EJBTHREE-1109. ;-) Which led to EJBTHREE-1110 (add a home load balance policy attribute), and with that the annotation is pretty EJB3 specific. So, I don't mind the annotation moving into ejb3-ext-api. anonymous wrote : | 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? :) | Hadn't drunk enough coffee; wasn't thinking clearly. If the goal is just to have no dependency from ejb3-ext-api and ejb3-impl to ha-client, it's not necessary. The aspects module classes have a dependency on ha-client, and that would "leak" back into ejb3-core. But ejb3-core is probably going to have the ha-client dependency anyway, via the clustered proxies. BTW, the above statement is based on my very vague understanding of the purpose of ejb3-impl vs. ejb3-core. If what I said makes no sense, please tell me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114397#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...