Hi Mark and Kurt, Thanks for your replies and recommendations. In the last couple of day, we investigated the Web services with COM approach. Unfortunately we found out that it is an invasive procedure(changes on the server) and requires a lot of setup. And is as you mentioned performance intensive. One of the reasons why we chose j-Interop for communication with COM was that it is completely non invasive . It is a pure java library implementing COM binary protocol, and its performance is acceptable to us. We are building a SAAS platform where we see a lot of potential for an ESB (currently we need to support SAP R/3). I apologise I cannot go much into details due to IP reason. As for point 1 by Kurt:- Sorry about the misunderstanding of "Listener", but from my point of understanding the notifier is only a special kind of action which listens on a channel. [service] [listeners/] [actions] [action/] <---- [/actions] [/service] May be we used an invalid naming? Please correct me if I am wrong. We will start the initial analysis and architecture of our gateway/bridge. Is it possible for us to post the papers here for review ? Thanks, best regards, Dirk View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131170#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...