Just to add some more confusion in here, there are actually 3 modes for our ESB.
(i) deploy into an application server/container.
(ii) deploy into the stand-alone server/container.
(iii) stand-alone server.
Which "standalone" do you mean? We haven't done much with (iii) for a while, so only really (i) and (ii) are illustrated within the docs and quickstarts.
By standalone mode I mean the one that uses this class :
I guess it is the (ii) one.
I wish I could have this class running a service on computer A and have JBoss ESB server 4.2.1GA running on computer B.
I haven't tried it yet, I don't even know if it is possible. I anyone knows just tell me.
Actually, I guess that the (i) mode suites most of the time in any company. But the standalone mode capability is important for me to explain ESB concepts to people.
This way I can demonstrate that ESB is an higly distributed solution (compared to hub an spoke EAI). And I think JBoss ESB is one, maybe thanks to the standalonebootstrapper, but I am not sure of this today.
This is the third option and it is demonstrated by most of the quickstarts.
The readme files with the quickstarts will explain how to do it.
You should be able to do what you want using (ii). There should really be no difference to (i) except for the types of services you might be able to host (e.g., no EJB3 implementations in (ii)). Give it a try.