Having had a look at the code, I would not recommend using it. Also I'm not sure that it is possible to configure this transport between two different applications (each having its own class loader) in the same VM.
Andreas On Tue, Mar 24, 2009 at 05:14, Asankha C. Perera <[email protected]> wrote: > >>>> which the OS will anyway stream through internally without placing on >>>> the >>>> >> >> NW interface. >> I thought local http traffic goes through the whole tcp stack, its little >> overkill when both Synapse and Webservice are in the same jvm. >> >> Any other transport choices available to get them to communicate, like >> straight java call? >> > > Yes, it will go through the TCP stack, but will be received immediately. I > would assume that keeping the ESB separate and enforcing hard modularity > would be more useful than trying to tweak in a bit more performance in this > case. > > You could get the ESB to load balance between a number of the service > implementations and give better performance. Also, Synapse performs > extremely well - if you need references let me know. Axis2 has a local > transport implementation, but I would think that it may not work straight > away with your Axis(1) services, but may be able to get it working rather > easily if you can spend some time on it > > cheers > asankha > > -- > Asankha C. Perera > AdroitLogic, http://adroitlogic.org > > http://esbmagic.blogspot.com > > > > >
