[
https://issues.apache.org/jira/browse/SYNAPSE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555489#action_12555489
]
Ruwan Linton commented on SYNAPSE-191:
--------------------------------------
I tried this sometime back in December and it worked. Is it possible to send
the xslt that you are using to transform the message so that I can have a look
again. It seems like the xslt transformer has an issue with the xsi namespace.
Further when I debug this I saw that the element fed to the xslt processor
contains the xsi namespace declaration.
> 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
> Assignee: Ruwan Linton
> Fix For: 1.1.1
>
> 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]
