ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: JBI BPEL->JBI XSLT
Date Wed, 02 Jan 2008 15:41:17 GMT
Hi Jan,

Since BPEL requires a WSDL description of the service, you would need to
write a dummy WSDL for Saxon.

Personally, I'd recommend looking at Apache Camel to create a pipeline at
combines both Ode and Saxon XSLT to transform the output.

alex


On 1/2/08, Jan Arend Jansen <nonose@xs4all.nl> wrote:
>
>
> Hi,
>
> I want to develop a scenario in BPEL using ODE and SAXON JBI and
> ServiceMix
> 3.2.
> The process is that an external trigger (via a BC) starts the BPEL ODE
> process. This process calls an external Web Service (again via a BC). The
> results needs to be transformed using an XSLT. I have tried to use the
> servicemix-saxon SU for that. It exposes the xslt on the JBI message bus
> and
> tranforms the message content.
>
> What I can't figure out is how to call a service endpoint on the JBI bus
> (the SAXON XSLT) that has no explicit WSDL. The XSLT SU has a servicename
> and an endpoint, but the operations and message are implicit (component
> just
> takes the body through XSLT and replies with the results).
>
> Any thoughts on how to approach this?
>
> Thanks,
> Jan Arend Jansen
> --
> View this message in context:
> http://www.nabble.com/JBI-BPEL-%3EJBI-XSLT-tp14578612p14578612.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message