axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirill Lastovirya (JIRA)" <>
Subject [jira] Commented: (AXIS2-1558) problem receiving escaped XML in payload
Date Tue, 09 Feb 2010 08:19:27 GMT


Kirill Lastovirya commented on AXIS2-1558:

Just want to leave some sensible resume, at least for stupid guy like me. The idea is that
in escaped XML only '<' character is to be escaped. '>' is ok to leave unescaped . This
is taken from XML definition. So Axis2 does not want to do excessive work and leave > signs

> problem receiving escaped XML in payload
> ----------------------------------------
>                 Key: AXIS2-1558
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: om
>    Affects Versions: nightly
>         Environment: 32-bit Windows
>            Reporter: Tony Dean
>            Assignee: Deepal Jayasinghe
> The following SOAP is sent from .NET to a org.apache.axis2.receivers.RawXMLINOutMessageReceiver
Axis2 endpoint:
> POST /axis2/services/myService HTTP/1.1
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.42)
> VsDebuggerCausalityData: uIDPoy26NIt2oGVMu3AaAaVfY/EAAAAAtJkH+jUVSkSoJtku7vQ/4n/vP3Qd2/BFs7BqUl9s3GUACAAA
> SOAPAction: ""
> Host: d4639:8080
> Content-Type: multipart/related; type="application/xop+xml"; boundary=--MIMEBoundary632978239375477793;
start="<>"; start-info="text/xml; charset=utf-8"
> Content-Length: 2018
> Expect: 100-continue
> Connection: Keep-Alive
> ----MIMEBoundary632978239375477793
> content-id: <>
> content-type: application/xop+xml; charset=utf-8; type="text/xml; charset=utf-8"
> content-transfer-encoding: binary
> <soap:Envelope xmlns:xop="" xmlns:soap=""
xmlns:xsi="" xmlns:xsd=""
xmlns:wsa="" xmlns:wsse=""
> wsu:Id="Timestamp-444822f9-5e62-401d-9537-85bff44e5248"><wsu:Created>2006-10-30T21:52:17Z</wsu:Created><wsu:Expires>2006-10-30T21:57:17Z</wsu:Expires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><copyintoout
r="3" g="2" b="1" /></parm14><parm15><String>hi15</String></parm15><parm16><IntegerRange
minValue="78" maxValue="89" /></parm16><parm17><Date>2006-10-30</Date></parm17></parameters><streams><instream><Value
> ----MIMEBoundary632978239375477793--
> Notice that .NET escaped the contents of the <Value> element.
> <Value xsi:type="xsd:string">&lt;TABLE&gt;&lt;InData&gt;&lt;col1&gt;1&lt;/col1&gt;&lt;col2&gt;2&lt;/col2&gt;&lt;/InData&gt;&lt;/TABLE&gt;</Value>
> When I receive the contents of the <Value> element at runtime, I see that Axis2
has the following content:
> <Value xmlns:xsi="" xsi:type="xsd:string">&lt;TABLE>&lt;InData>&lt;col1>1&lt;/col1>&lt;col2>2&lt;/col2>&lt;/InData>&lt;/TABLE></Value>
> Notice that &lt; is still escaped, but the &gt; are unescaped.  When I ask the
Axis2 engine for <Value> children, it thinks that it has none.  <TABLE> should
be its one and only child element.
> Can someone explain what's going on here?  Why < remains escaped as &lt; and >
are unescaped.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message