I am looking at this now. Just for the record, there has been some previous discussion on this issue: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=117224 For security the situation is a bit better, if I remember correctly. In the security stuff I don't think there is a hardcoded dependency on a class. The security dependency is already an interface, which could simply be moved to an integration project. For transactions, the interface needs to be created. I did this already -- it's a very simple interface, with a single method that returns a Transaction instance associated with the incoming request. I am not quite familar with maven yet, so setting up the maven build for the integration project is what will take me more time. Which makes me think if I am on the right track or not... Do we really want an integration project and a jboss-corba-ots-spi jar containing just a single class file for an interface with a single method? | interface InboundTransactionCurrent { | javax.transaction.Transaction getCurrentTransaction(); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086342#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...