[
https://wso2.org/jira/browse/ESBJAVA-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28006#action_28006
]
Hiranya Jayathilaka commented on ESBJAVA-578:
---------------------------------------------
In latest Carbon based ESB builds XML content is handled properly. Encoding and
decoding of special XML characters is handled correctly.
> when storing text as a property, < is correctly translated on the way in, but
> when accessing the property, it remains as <
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-578
> URL: https://wso2.org/jira/browse/ESBJAVA-578
> Project: WSO2 ESB
> Issue Type: Bug
> Affects Versions: 1.7.1
> Environment: linux, ESB 1.7.1
> Reporter: michael williams
> Assignee: Hiranya Jayathilaka
>
> I'm setting a property to be something like <Element Name>value</Element
> Name> as text instead of XML fragment. I have reasons for doing this ...
> when I look at the configuration file, the local entry is stored as:
> <Element Name%gt;value</Element Name> as would be expected.
> However, when I retrieve the property inside using an expression (adding it
> to a header), the result is: <Element Name>value</ElementName> ...
> such that the < remains as < ... this behavior makes the result unusable
> as the message content especially for use on the Callout Mediator.
> Please help!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
