This topic is pulled from a tangential discussion on: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=109907 I'd noted before that we may move the following classes: "ALRubinger" wrote : PojiProxy | Remoting | AOPRemotingInvocationHandler ...from jboss-remoting-aspects into a new Remoting-esque project, where I'd also cited: "ALRubinger" wrote : Only thing we get by moving it out is an organizational benefit. This is incorrect, given https://jira.jboss.org/jira/browse/JBASPECT-3. The issue is that jboss-remoting-aspects holds these convenience classes which also create a dependency upon the Tx and Security aspects, violating the orthogonal nature of an aspect-based project. So the question remaining is, where to put the new project? http://anonsvn.jboss.org/repos/jbossas/projects/integration/trunk/ - Contains SPIs, so this doesn't seem like a great fit http://anonsvn.jboss.org/repos/jbossas/projects/remoting - Seems misleading, this is not the Remoting project itself, but rather some convenience mechanisms to using Remoting alongside jboss-aspects. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166816#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...