xslt for both in-only and in-out from http consumer

[johper <ka...@hotmail.com>]

Hi,

Would like to deploy a WSDL file containing portType with operations 
for both input/output and input only.

When this WSDL file is deployed in SMX I use InOut MEP for the HTTP consumer
and it works fine when I provides all calls "as is" to another implementing
node.
The InOut declared HTTP consumer handles both InOut and InOnly 
(all portType operations in WSDL) method calls from client node.

Now I need to XSLT/transform every call before providing it to another
SOAP implementation.

I have tried two ways of XSLT/transforming every operation:

1) HTTP consumer <-> EIP:static-routing-slip <-> XSLT <-> HTTP provider
this works fine for InOut but not for InOnly

2) HTTP consumer -> EIP:pipeline -> XSLT -> HTTP provider
this works fine for InOnly but not for InOut

Question is how to do this, I have to split based on MEP ?

Thanks in advance

-- 
View this message in context: http://www.nabble.com/xslt-for-both-in-only-and-in-out-from-http-consumer-tp15048952s12049p15048952.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: xslt for both in-only and in-out from http consumer

[johper <ka...@hotmail.com>]

Added cbr (content based router) between http-consumer and xslt processing,
it works.

http-consumer sends to cbr and cbr sends to pipeline for in-only metods and
to a static-routing-slip for in-out metods. Now xslt can be applied on both
mep types.


johper wrote:
> 
> Hi,
> 
> Would like to deploy a WSDL file containing portType with operations 
> for both input/output and input only.
> 
> When this WSDL file is deployed in SMX I use InOut MEP for the HTTP
> consumer
> and it works fine when I provides all calls "as is" to another
> implementing node.
> The InOut declared HTTP consumer handles both InOut and InOnly 
> (all portType operations in WSDL) method calls from client node.
> 
> Now I need to XSLT/transform every call before providing it to another
> SOAP implementation.
> 
> I have tried two ways of XSLT/transforming every operation:
> 
> 1) HTTP consumer <-> EIP:static-routing-slip <-> XSLT <-> HTTP provider
> this works fine for InOut but not for InOnly
> 
> 2) HTTP consumer -> EIP:pipeline -> XSLT -> HTTP provider
> this works fine for InOnly but not for InOut
> 
> Question is how to do this, I have to split based on MEP ?
> 
> Thanks in advance
> 
> 

-- 
View this message in context: http://www.nabble.com/xslt-for-both-in-only-and-in-out-from-http-consumer-tp15048952s12049p15063945.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: xslt for both in-only and in-out from http consumer

[johper <ka...@hotmail.com>]

Added cbr (content based router) between http-consumer and xslt processing,
it works.

http-consumer sends to cbr and cbr sends to pipeline for in-only metods and
to a static-routing-slip for in-out metods. Now xslt can be applied on both
mep types.


johper wrote:
> 
> Hi,
> 
> Would like to deploy a WSDL file containing portType with operations 
> for both input/output and input only.
> 
> When this WSDL file is deployed in SMX I use InOut MEP for the HTTP
> consumer
> and it works fine when I provides all calls "as is" to another
> implementing node.
> The InOut declared HTTP consumer handles both InOut and InOnly 
> (all portType operations in WSDL) method calls from client node.
> 
> Now I need to XSLT/transform every call before providing it to another
> SOAP implementation.
> 
> I have tried two ways of XSLT/transforming every operation:
> 
> 1) HTTP consumer <-> EIP:static-routing-slip <-> XSLT <-> HTTP provider
> this works fine for InOut but not for InOnly
> 
> 2) HTTP consumer -> EIP:pipeline -> XSLT -> HTTP provider
> this works fine for InOnly but not for InOut
> 
> Question is how to do this, I have to split based on MEP ?
> 
> Thanks in advance
> 
> 

-- 
View this message in context: http://www.nabble.com/xslt-for-both-in-only-and-in-out-from-http-consumer-tp15048952s12049p15063945.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.