[prev in list] [next in list] [prev in thread] [next in thread]
List: axis-c-user
Subject: SV: Problem with AXIOM Handling of Newlines and Spaces in SOAP
From: Pankaj Kharwal <Pankaj.Kharwal () kf ! se>
Date: 2011-12-08 17:07:44
Message-ID: B40A0E70620A7A4AA3822397B7677B1F04AE2AEEB0 () STO-MBX-06 ! kf ! local
[Download RAW message or body]
Dear all,
Any inputs/suggestions/ideas?
Thanks and Regards,
Pankaj Kharwal
Stockholm, Sweden
Från: Pankaj Kharwal
Skickat: den 30 november 2011 11:50
Till: 'c-user@axis.apache.org'
Ämne: Problem with AXIOM Handling of Newlines and Spaces in SOAP requests
Hi All,
I am using AXIS2C version 1.6.0 on an X86 64-bit Redhat machine. I use soapUI for \
sending requests and AXIS2C receives newlines and spaces in the request which I \
cannot control from the request part.
For example, My soapUI request looks like:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" \
xmlns:typ="http://ws.apache.org/axis2/services/Calculator/types"> <soapenv:Header/>
<soapenv:Body>
<typ:add xmlns:typ = 'http://example.com/add/2010/11/policy'>
<param_1>11</param_1>
<param_2>22</param_2>
</typ:add>
</soapenv:Body>
</soapenv:Envelope>
Here, axiom_node_to_string() function for <add> node yields "<typ:add xmlns:typ = \
'http://example.com/add/2010/11/policy'>\n <param_1>11</param_1>\n \
<param_2>22</param_2>\n </typ:add>" I thought I will first convert this node to \
a buffer (addBuf); then I will process this buffer to remove newlines; and then I \
will pass the processed buffer to axiom_xml_reader_create_for_memory().
So the sequence of my calls is:
reader = axiom_xml_reader_create_for_memory(env, (void*)addBuf, \
axutil_strlen(addBuf), "utf-8", AXIS2_XML_PARSER_TYPE_BUFFER); builder = \
axiom_stax_builder_create(env, reader); document = \
axiom_stax_builder_get_document(builder, env); processedAddNode = \
axiom_document_get_root_element(document, env);
My observations:
1. CASE1: addBuf is passed as it is (with newlines and spaces) to \
axiom_xml_reader_create_for_memory. The call to axiom_xml_reader_create_for_memory() \
is successful; but the processedAddNode does not have <param_1> and <param_2> tags.
2. CASE2: Before calling axiom_xml_reader_create_for_memory, I process addBuf \
just to remove newlines. addBuf looks like "<typ:add xmlns:typ = \
'http://example.com/add/2010/11/policy'> <param_1>11</param_1> \
<param_2>22</param_2> </typ:add>". The spaces that existed after the newlines, \
still remain there. Here also, the call to axiom_xml_reader_create_for_memory() is \
successful; but the processedAddNode does not have <param_1> and <param_2> tags.
3. CASE3: I hardcoded addBuf to "<typ:add xmlns:typ = \
'http://example.com/add/2010/11/policy'><param_1>11</param_1><param_2>22</param_2></typ:add>". \
Note that the newlines are removed and spaces after the newlines were also removed. \
This time call to axiom_xml_reader_create_for_memory() was successful. \
processedAddNode was perfect.
So, if there are any spaces after the ending tags, AXIOM does not seem to handle them \
very well. Of course, I can process the buffer to remove these obsolete spaces as \
well, but I have a gut feeling that AXIOM must have some efficient mechanism, which I \
am not aware of as of now, to handle this situation.
I would be really thankful if you could provide me any ideas on implementing better \
mechanisms for this.
Best Regards,
Pankaj Kharwal
Stockholm, Sweden
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
[Attachment #3 (text/html)]
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:p="urn:schemas-microsoft-com:office:powerpoint" \
xmlns:a="urn:schemas-microsoft-com:office:access" \
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" \
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" \
xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" \
xmlns:b="urn:schemas-microsoft-com:office:publisher" \
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" \
xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" \
xmlns:odc="urn:schemas-microsoft-com:office:odc" \
xmlns:oa="urn:schemas-microsoft-com:office:activation" \
xmlns:html="http://www.w3.org/TR/REC-html40" \
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" \
xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" \
xmlns:Repl="http://schemas.microsoft.com/repl/" \
xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" \
xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" \
xmlns:ppda="http://www.passport.com/NameSpace.xsd" \
xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" \
xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" \
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" \
xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" \
xmlns:udc="http://schemas.microsoft.com/data/udc" \
xmlns:xsd="http://www.w3.org/2001/XMLSchema" \
xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" \
xmlns:ec="http://www.w3.org/2001/04/xmlenc#" \
xmlns:sp="http://schemas.microsoft.com/sharepoint/" \
xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" \
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \
xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" \
xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" \
xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" \
xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" \
xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" \
xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" \
xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" \
xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" \
xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" \
xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" \
xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" \
xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" \
xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" \
xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" \
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.E-postmall18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.E-postmall19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1673802437;
mso-list-type:hybrid;
mso-list-template-ids:-1773083724 69009423 69009433 69009435 69009423 69009433 \
69009435 69009423 69009433 69009435;} @list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=SV link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Dear all, <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Any \
inputs/suggestions/ideas?<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal>Thanks and Regards, <o:p></o:p></p>
<p class=MsoNormal>Pankaj Kharwal<o:p></o:p></p>
<p class=MsoNormal>Stockholm, Sweden<o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Från:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Pankaj Kharwal <br> \
<b>Skickat:</b> den 30 november 2011 11:50<br> <b>Till:</b> \
'c-user@axis.apache.org'<br> <b>Ämne:</b> Problem with AXIOM Handling of Newlines and \
Spaces in SOAP requests<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi All, <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I am using AXIS2C version 1.6.0 on an X86 64-bit
Redhat machine. I use soapUI for sending requests and AXIS2C receives newlines
and spaces in the request which I cannot control from the request \
part.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>For example, My soapUI request looks like:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://ws.apache.org/axis2/services/Calculator/types"><o:p></o:p></p>
<p class=MsoNormal> <soapenv:Header/><o:p></o:p></p>
<p class=MsoNormal> <soapenv:Body><o:p></o:p></p>
<p class=MsoNormal> <typ:add xmlns:typ = \
'http://example.com/add/2010/11/policy'><o:p></o:p></p>
<p class=MsoNormal>
<param_1>11</param_1><o:p></o:p></p>
<p class=MsoNormal>
<param_2>22</param_2><o:p></o:p></p>
<p class=MsoNormal> </typ:add><o:p></o:p></p>
<p class=MsoNormal> </soapenv:Body><o:p></o:p></p>
<p class=MsoNormal></soapenv:Envelope><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Here, axiom_node_to_string() function for <add> node
yields ”<typ:add xmlns:typ = \
'http://example.com/add/2010/11/policy'>\n
<param_1>11</param_1>\n
<param_2>22</param_2>\n
</typ:add>”<o:p></o:p></p>
<p class=MsoNormal>I thought I will first convert this node to a buffer
(addBuf); then I will process this buffer to remove newlines; and then I will
pass the processed buffer to axiom_xml_reader_create_for_memory().<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>So the sequence of my calls is:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>reader = axiom_xml_reader_create_for_memory(env,
(void*)addBuf, axutil_strlen(addBuf), "utf-8",
AXIS2_XML_PARSER_TYPE_BUFFER);<o:p></o:p></p>
<p class=MsoNormal>builder = axiom_stax_builder_create(env, reader);<o:p></o:p></p>
<p class=MsoNormal>document = axiom_stax_builder_get_document(builder, \
env);<o:p></o:p></p>
<p class=MsoNormal>processedAddNode = axiom_document_get_root_element(document,
env);<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>My observations:<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if \
!supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New \
Roman"'> </span></span><![endif]>CASE1: addBuf is \
passed as it is (with newlines and spaces) to axiom_xml_reader_create_for_memory. The \
call to axiom_xml_reader_create_for_memory() is successful; but the processedAddNode \
does not have <param_1> and <param_2> tags.<o:p></o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if \
!supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New \
Roman"'> </span></span><![endif]>CASE2: Before \
calling axiom_xml_reader_create_for_memory, I process addBuf just to remove newlines.
addBuf looks like ”<typ:add xmlns:typ =
'http://example.com/add/2010/11/policy'>
<param_1>11</param_1>
<param_2>22</param_2>
</typ:add>”. The spaces that existed after the newlines, still remain
there. Here also, the call to axiom_xml_reader_create_for_memory() is successful;
but the processedAddNode does not have <param_1> and <param_2>
tags. <o:p></o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if \
!supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New \
Roman"'> </span></span><![endif]>CASE3: I \
hardcoded addBuf to ”<typ:add xmlns:typ = \
'http://example.com/add/2010/11/policy'><param_1>11</param_1><param_2>22</param_2></typ:add>”.
Note that the newlines are removed and spaces after the newlines were
also removed. This time call to axiom_xml_reader_create_for_memory() was
successful. processedAddNode was perfect.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>So, if there are any spaces after the ending tags, AXIOM does
not seem to handle them very well. Of course, I can process the buffer to
remove these obsolete spaces as well, but I have a gut feeling that AXIOM must
have some efficient mechanism, which I am not aware of as of now, to handle
this situation.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I would be really thankful if you could provide me any ideas
on implementing better mechanisms for this.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Best Regards, <o:p></o:p></p>
<p class=MsoNormal>Pankaj Kharwal<o:p></o:p></p>
<p class=MsoNormal>Stockholm, Sweden<o:p></o:p></p>
</div>
<br clear="both">
______________________________________________________________________<BR>
This email has been scanned by the Symantec Email Security.cloud service.<BR>
For more information please visit http://www.symanteccloud.com<BR>
______________________________________________________________________<BR>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic