I've checked in the refactoring for the new integration layer etc. Each layer is compiled separately and the result added to a separate jar, so we have. JBM core, Core now has no dependencies on anything else. The resulting classes are archived in jbm-core.jar and jbm-client-core.jar. The latter still needs tidying up as it still contains some classes that probably should only be server side. Transports. The netty and mina implementations of remoting now live under org.jboss.messaging.integration.transports. They depend on core and obviously netty and mina for compilation. These are the archived to jbm-transports.jar. I've left the invm transport in core i wasn't sure whether to do that or move it as well. If i do move then at least the pckage names would be consistent, wdyt? Security, The jbossas security manager has been moved to org.jboss.messaging.integration.security. Again I've left the basic security manager in core as it has no dependencies, I'll move this if we decide to move the invm transport to be consistent. Logging, Logger now uses java.util.Logger. I've also added to handlers under org.jboss.messaging.logging, one for the jboss logger and one for log4j. These can be used by changing the handlers configured in logging.properties under jre/lib. Ive added one under src/etc that uses the jboss logge We need this for when we bootstrap using the MC since if we don't provide a jboss logger plugin, aop defaults all of its logging to stdout. the tests/examples etc use the default java.util.logger. I still have a bit more tidying up to do, i need to test all the examples etc still work. Any issues let me know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188751#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...