Hello Alex, Recommendation of using Camel is interesting..can you please share some example on the usage? Regards,
Vishal Bhasin ----- Original Message ---- From: Alex Boisvert <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, January 2, 2008 9:41:17 AM Subject: Re: JBI BPEL->JBI XSLT 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 <[EMAIL PROTECTED]> 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. > > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
