[jboss-jira] [JBoss JIRA] (JBAS-9529) CXF not correctly escaping >

[Alessio Soldano (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752851#comment-12752851 ] 

Alessio Soldano commented on JBAS-9529:
---------------------------------------

Hi Kelly,
ok, I think this discussion should be carried on on a forum thread (https://community.jboss.org/en/jbossws/cxf), possibly with some code showing exactly what you're trying to do; me or anybody else might possibly try reproducing your scenario and suggest fixes. You're not directly using the apache cxf that's in AS 6.1.0 and which the jbossws integration there has been tested with, so this is basically a matter of figuring out what's wrong, if any, in cxf.
I'm closing this jira because in any case no fix will likely be required in JBoss AS/WS and even it will be required nothing will be committed on AS 6 codebase, given on community side it's currently replaced by the AS7 dev line.
                
> CXF not correctly escaping >
> -------------------------------
>
>                 Key: JBAS-9529
>                 URL: https://issues.jboss.org/browse/JBAS-9529
>             Project: Application Server 3  4  5 and 6
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: 6.1.0
>         Environment: RHEL 5
>            Reporter: Eric Schley
>            Assignee: Alessio Soldano
>
> We have a string containing > (literally > not >) and we are trying to return it in a response but it is getting converted into >.  I would have thought if any escaping occurred it would have possibly converted it to > and then back to >
> We were using encoding of UTF-8.  We did notice that if we were using ISO-8859-1 this would occur so we aren't sure if somewhere within its processing it may be defaulting to ISO-8859-1 and then passing it back up.
> using apache CXF 2.5.1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira