[
https://issues.apache.org/jira/browse/SYNAPSE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556808#action_12556808
]
Asankha C. Perera commented on SYNAPSE-191:
-------------------------------------------
Andreas
Sorry for the confusion.. I made a slight mistake in saying this is a duplicate
- whereas the resolution for this would require the solution for 187..
The actual XSLT output for this case provided my Matt generates two elements -
and when we parse this into XML again to be included back into the message, we
retain only the first element. So the fix for this exact issue is to specify
source="//env:Body" and wrap the XSLT output into a "env:Body" element, which
will replace the original body back again.. Due to maintaining confidentiality
of the actual XSLT I am unable to paste it here, but I guess this description
will help make things clear
asankha
> 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: Asankha C. Perera
> Fix For: 1.1.1-QA-B2
>
> 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]
