Thanks Indika, I will try out the Smooks mediator. In the meanwhile I have 
doing some experimentation and I was wondering is there some merit and having 
the input/output streams also available besides message.envelope.body access? I 
am aware that if the users muddle with the payload we could have some problems 
but if they know what they are doing then the transformations on the stream can 
be cheaper in terms of hardware resources (CPU & Memory required (1% or 2% cpu 
overhead & about 5K read-ahead memory - I have tried that out by extending 
Synapse's Axis2 HTTP Sender). Would like to know your thoughts?

Thanks,
Cylus

________________________________________
From: indika kumara [[email protected]]
Sent: Wednesday, August 18, 2010 11:40 AM
To: [email protected]
Subject: Re: Parsing XML Response

 Hi Cylus

 Sorry for late reply, I have not been touching with the Synapse's mailing
list for last few weeks ...

  It is in [1]. It was implemented for a special user for supporting
specific requirements. It uses the concept of fragment-based processing,
which is employed by Smooks too.

  I believe there should be a Smooks mediator WSO2 ESB 3.0.0 release. You
may try that.

 Thanks

 Indika

 [1] http://wso2.org/svn/browse/wso2/people/indika/mediators/

code is though. Indika?
>
> Also, these sort of requirements can be handled by Smooks a transformation
> library which can be converted to a mediator. To answer question on adding
> logic to endpoint to process the response, it is not possible, becuase of
> the asynchronous behavior of the synapse engine. When you call
> endpoint.send
> the method returns before getting the response, actually even before the
> message sending being completed.
>
> Thanks,
> Ruwan
>
> On Fri, Aug 6, 2010 at 4:43 AM, Penkar, Cylus <[email protected]> wrote:
>
> > Folks,
> >
> > We have a need to further process the response returned by a SOAP service
> > to do some transformation on it. XSLT mediator will not work IMHO because
> > the response is huge and correct me if I am wrong but it will definitely
> > slow down processing.
> >
> > 1)      Is there a way to get access to XML stream processing?
> > 2)      Can we insert logic in the endpoint to transform the response as
> > the response stream is being read?
> >
> > Thanks,
> > Cylus
> >
> >
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: [email protected]; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>

Reply via email to