[
https://issues.apache.org/jira/browse/SYNAPSE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551498
]
Matt Shaw commented on SYNAPSE-191:
-----------------------------------
Hi Ruwan,
I've turned on logging and looked through the files. The XSL stylesheet adds
some header info and then starts to process the message document and basically
copies the elements into a new enclosing element. There are no errors in the
log but the copy elements (i.e. the first interaction with the message which
contains the xsi use) fails and what gets returned is just the header added by
the stylesheet. If I remove any reference to xsi in the main web service
everything works ok. Unfortunately there are web services that we use that are
out of our control to change.
Matt
> XLST Mediator Issue when using xsi namespace in the Body of Message
> -------------------------------------------------------------------
>
> Key: SYNAPSE-191
> URL: https://issues.apache.org/jira/browse/SYNAPSE-191
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1
> Environment: wso2esb-1.6-qa-b1, Java 1.5.0, Windows XP SP2
> Reporter: Matt Shaw
> Attachments: WebServiceResponse.xml
>
>
> When using the XSLT mediator to transform the result of a proxied web
> service. If the proxied web service returns elements that use the xsi
> namespace within the Body, the XSLT transform fails. I believe this is
> because the xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; definition
> is normally contained within the Envelope element but when the XSLT meditor
> is invoked only the contents of the Body element are passed to the XSLT
> mediator. Therefore the new XML fragment is not atomic and complete because
> the xsi defintion is lost.
> Thanks
> Matt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
