Well the key here is to process the SOAP message as the intermediary is completely dependent on it. So I think given the context and ServiceMIX being a proper implementation of the JBI Specification it won't be the right approach.
But I would like to know if there is anyone who is using it to only process SOAP - from a SOA standpoint. Best regards Soumadeep On Fri, Sep 11, 2009 at 7:59 PM, Guillaume Nodet <[email protected]> wrote: > I think it depends on the components you're using. > I think both servicemix-http and servicemix-cxf-bc can be configured > to pass the whole payload without any soap processing at all. > For servicemix-http, if you use a <http:consumer/> endpoint, you could > have access to the underlying stream directly and bypass the whole > soap processing. > > On Fri, Sep 11, 2009 at 14:41, Soumadeep Sen <[email protected]> > wrote: > > Hi Guillaume, > > > > We are working on a WS Intermediary using ServiceMix but the problem is > that > > SMX assumes that components are heterogeneous and talk in different data > > format and SMX converts the message from native to jbi and jbi to native > . > > This is causing a huge performance issue. > > > > I fully understand that the purpose of JBI was to exactly do this but > then > > in the given context where all components talk SOAP its becoming a > bottle > > neck. > > > > Can we have some kind of a work around? > > > > Best regards > > Soumadeep > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
