You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Edward Manmohan <ed...@gmail.com> on 2007/06/08 08:30:21 UTC
XSLT transform back functionality on servicemix
Hi,
I have configured the servicemix to route to my service after an xslt
transformation on the request and got the response back to the client. I
have used the static-routing-slip eip component in-order to achieve this
because I want the in-out MEP to be present.
Now I want the response message to be transformed from another transform
back XSLT, keeping the in-out MEP.
Can anyone have any idea on how this can be done?
Thanks,
-Edward-
Re: XSLT transform back functionality on servicemix
Posted by Gert Vanthienen <ge...@skynet.be>.
Edward,
AFAIK, there is no out-of-the-box way to do this. Personally, I would
create a Java class for servicemix-lwcontainer that:
- receives the in message
- translates it
- executes a new in-out message exchange
- translates the result
- answers the original message
The question has been asked before, so if you're interested in building
a more generic solution and contributing it to ServiceMix, you're more
than welcome. Just raise a JIRA and let us know if we can help you with
anything...
Regards,
Gert
Edward Manmohan wrote:
> Correction
>
> /s/Can/Is
>
> On 6/8/07, Edward Manmohan <ed...@gmail.com> wrote:
>>
>> Hi,
>>
>> I have configured the servicemix to route to my service after an xslt
>> transformation on the request and got the response back to the client. I
>> have used the static-routing-slip eip component in-order to achieve this
>> because I want the in-out MEP to be present.
>>
>> Now I want the response message to be transformed from another transform
>> back XSLT, keeping the in-out MEP.
>>
>> *Is* anyone have any idea on how this can be done?
>>
>> Thanks,
>> -Edward-
>
Re: XSLT transform back functionality on servicemix
Posted by Edward Manmohan <ed...@gmail.com>.
Correction
/s/Can/Is
On 6/8/07, Edward Manmohan <ed...@gmail.com> wrote:
>
> Hi,
>
> I have configured the servicemix to route to my service after an xslt
> transformation on the request and got the response back to the client. I
> have used the static-routing-slip eip component in-order to achieve this
> because I want the in-out MEP to be present.
>
> Now I want the response message to be transformed from another transform
> back XSLT, keeping the in-out MEP.
>
> *Is* anyone have any idea on how this can be done?
>
> Thanks,
> -Edward-
Re: XSLT transform back functionality on servicemix
Posted by Gert Vanthienen <ge...@skynet.be>.
-Ed-,
Can you retry it with the second XSLT in the routing slip and post the
resulting stack trace?
Gert
Ruwan Linton wrote:
> On 6/8/07, Guillaume Nodet <gn...@gmail.com> wrote:
>>
>> Just add another XSLT transformation in your routing slip, after the
>> actual
>> service, so you would have:
>> xslt -> service -> xslt
>
>
> I have done this before sending to the list,
>
> But this did not work for me. I got an error saying that unable to send
> back the response, in the in-out MEP.
>
> Any other help? Or any thing that I have to say in the eip target-exchange?
> Have U tried whether this working or not?
>
> Thanks for the help,
>
> -Ed-
>
> On 6/8/07, Edward Manmohan <ed...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I have configured the servicemix to route to my service after an xslt
>> > transformation on the request and got the response back to the
>> client. I
>> > have used the static-routing-slip eip component in-order to achieve
>> this
>> > because I want the in-out MEP to be present.
>> >
>> > Now I want the response message to be transformed from another
>> transform
>> > back XSLT, keeping the in-out MEP.
>> >
>> > Can anyone have any idea on how this can be done?
>> >
>> > Thanks,
>> > -Edward-
>> >
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Principal Engineer, IONA
>> Blog: http://gnodet.blogspot.com/
>>
>
>
>
Re: XSLT transform back functionality on servicemix
Posted by Ruwan Linton <ru...@gmail.com>.
On 6/8/07, Guillaume Nodet <gn...@gmail.com> wrote:
>
> Just add another XSLT transformation in your routing slip, after the
> actual
> service, so you would have:
> xslt -> service -> xslt
I have done this before sending to the list,
But this did not work for me. I got an error saying that unable to send
back the response, in the in-out MEP.
Any other help? Or any thing that I have to say in the eip target-exchange?
Have U tried whether this working or not?
Thanks for the help,
-Ed-
On 6/8/07, Edward Manmohan <ed...@gmail.com> wrote:
> >
> > Hi,
> >
> > I have configured the servicemix to route to my service after an xslt
> > transformation on the request and got the response back to the client. I
> > have used the static-routing-slip eip component in-order to achieve this
> > because I want the in-out MEP to be present.
> >
> > Now I want the response message to be transformed from another transform
> > back XSLT, keeping the in-out MEP.
> >
> > Can anyone have any idea on how this can be done?
> >
> > Thanks,
> > -Edward-
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Principal Engineer, IONA
> Blog: http://gnodet.blogspot.com/
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: XSLT transform back functionality on servicemix
Posted by Guillaume Nodet <gn...@gmail.com>.
Just add another XSLT transformation in your routing slip, after the actual
service, so you would have:
xslt -> service -> xslt
On 6/8/07, Edward Manmohan <ed...@gmail.com> wrote:
>
> Hi,
>
> I have configured the servicemix to route to my service after an xslt
> transformation on the request and got the response back to the client. I
> have used the static-routing-slip eip component in-order to achieve this
> because I want the in-out MEP to be present.
>
> Now I want the response message to be transformed from another transform
> back XSLT, keeping the in-out MEP.
>
> Can anyone have any idea on how this can be done?
>
> Thanks,
> -Edward-
>
--
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/