I still don't understand where your problem is. If you don't want soap processing because of the overhead, you can pass the whole message and by pass soap. If you want soap processing, there will be an overhead. You can't have both at the same time. Could you be a bit more explicit in what you're looking for ?
On Fri, Sep 11, 2009 at 19:44, Soumadeep Sen <[email protected]> wrote: > yeah, I remember that... but it was more of a hack. > Guillaume, any thoughts? > > -Soumadeep > Bizsensors > > On Fri, Sep 11, 2009 at 11:10 PM, vikas kumar <[email protected]>wrote: > >> Hi Soumadeep, >> >> We had used Servicemix-3.0 for something similar. What you can do is >> >> 1. Leave the normalized message empty (or add some dummy content to it) >> 2. Set the SOAP and other objects as properties in the exchange itself >> 3. Copy the exchange's properties to every other exchange you create (to >> talk to other components) >> >> This saves the system from repeated marshaling and un-marshaling (it >> atleast >> did in the earlier versions), not sure if that is the case now. >> >> Best regards, >> ~Vikas >> >> On Fri, Sep 11, 2009 at 9:50 PM, Guillaume Nodet <[email protected]> wrote: >> >> > So if you want it to be processed, it has some extra overhead. Not >> > sure what we can really do about it but trying to optimize it if >> > possible. Usually only the beginning of the message will be parsed and >> > the body will not be read until requested by the next component. >> > >> > On Fri, Sep 11, 2009 at 18:08, Soumadeep Sen <[email protected]> >> wrote: >> > > As a Binding Component... >> > > >> > > On Fri, Sep 11, 2009 at 9:16 PM, Guillaume Nodet <[email protected]> >> > wrote: >> > > >> > >> I don't really understand. >> > >> Do you want to process the SOAP envelope at the BC level or let it go >> > >> through the NMR ? >> > >> >> > >> On Fri, Sep 11, 2009 at 16:55, Soumadeep Sen <[email protected]> >> > wrote: >> > >> > 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 >> > >> >> >> > >> > >> > >> >> > >> >> > >> >> > >> -- >> > >> Cheers, >> > >> Guillaume Nodet >> > >> ------------------------ >> > >> Blog: http://gnodet.blogspot.com/ >> > >> ------------------------ >> > >> Open Source SOA >> > >> http://fusesource.com >> > >> >> > > >> > >> > >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > ------------------------ >> > Blog: http://gnodet.blogspot.com/ >> > ------------------------ >> > Open Source SOA >> > http://fusesource.com >> > >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
