http://cvs.apache.org/dist/soap/nightly/2005-06-27/ has a better implementation which should restore the DOS protection while expanding the entities described in "2.4 Character Data and Markup" in XML 1.0.
Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. ----- Original Message ----- From: "Werner Lehmann" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, June 27, 2005 12:25 PM Subject: Re: XML payload not working in latest nightly build? > Hi Scott, > > thanks for the prompt update. It is working just fine so we can remove > the Base64 encoding workaround again :-) > > Werner > > > Scott Nichol wrote: > > There is a new nightly build at > > http://cvs.apache.org/dist/soap/nightly/2005-06-24/. I believe it fixes > > the problem you have had. > > > > Scott Nichol > > > > Do not send e-mail directly to this e-mail address, > > because it is filtered to accept only mail from > > specific mail lists. > > ----- Original Message ----- > > From: "Scott Nichol" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Friday, June 24, 2005 12:58 PM > > Subject: Re: XML payload not working in latest nightly build? > > > > > > I am looking into this and can duplicate the error. > > > > The Client class now has a setUseDocumentBuilder method. When this is set > > to false, the current code seems to work correctly. When it is true, which > > is the default, the error you observe occurs. > > > > I will let you know when I have fixed this. > > > > Scott Nichol > > > > Do not send e-mail directly to this e-mail address, > > because it is filtered to accept only mail from > > specific mail lists. > > ----- Original Message ----- > > From: "Werner Lehmann" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Friday, June 24, 2005 10:10 AM > > Subject: Re: XML payload not working in latest nightly build? > > > > > > > >>Hi Scott, > >> > >>answers inline below: > >> > >>Scott Nichol wrote: > >> > >>>Can you be more specific? > >>> > >>>1. Are you using the nightly build on the client, server or both? > >> > >>Both. > >> > >> > >>>2. Is this problem the data sent from the client or server? > >> > >>It is from the server. > >> > >> > >>>3. What tool are you using to view the payload? > >> > >>We are debugging on the client with IBM Websphere and inspecting the > >>body with the debugger. There is no implicit XML/string processing. > >> > >> > >>>4. Are you using the RPC or messaging API? > >> > >>RPC. > >> > >> > >>>5. Does "XML payload" refer to the whole SOAP message, or > >>> just a paramter you are sending? > >> > >>It is the return value. > >> > >>Both stable and nightly build deliver this on the client: > >> > >> lResponse.getBodyPart(0).getContent().toString() --> > >> > >>><?xml version= '1.0' encoding= 'UTF-8' ?> > >>><SOAP-ENV:Envelope xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance"; > >>>xmlns:xsd= "http://www.w3.org/2001/XMLSchema"; xmlns:SOAP-ENV= > >>>"http://schemas.xmlsoap.org/soap/envelope/"; > > >>> > >>><SOAP-ENV:Body> > >>><ns1:mintGetMainConfigurationAPIResponse xmlns:ns1= "urn:mint:mandator" > >>>SOAP-ENV:encodingStyle= "http://schemas.xmlsoap.org/soap/encoding/"; > > >>> > >>>< return xmlns:ns2= "urn:mint" xsi:type= "ns2:MintResultString" > > >>><reasonCode xsi:type= "xsd:string" ></reasonCode> > >>><responseTimes xmlns:ns3= "http://schemas.xmlsoap.org/soap/encoding/"; > >>>xsi:type= "ns3:Array" ns3:arrayType= "xsd:long[2]" > > >>><item xsi:type= "xsd:long" >31</item> > >>><item xsi:type= "xsd:long" >31</item> > >>></responseTimes> > >>><returnCode xsi:type= "xsd:int" >0</returnCode> > >>><values xmlns:ns4= "http://schemas.xmlsoap.org/soap/encoding/"; xsi:type= > >>>"ns4:Array" ns4:arrayType= "xsd:string[1]" > > >>><item xsi:type= "xsd:string" ><?xml version="1.0" > >>>encoding="UTF-8"?> > >>><WEB_MENU VERSION="1.0"><WEB_MENU_ITEM > >>>title="WEB_MENU-HOME"><WEB_MENU_ITEM_USECASE > >>>text="WEB_USE_CASE-WELCOME" image="IMG-WELCOME" > >>>action_id="1" /><WEB_MENU_ITEM_USECASE > >>>text="WEB_USE_CASE-MY_RECORDS" image="IMG-MY_RECORDS" > >>>action_id="2" /><WEB_MENU_ITEM_USECASE > >>>text="WEB_USE_CASE-MY_SCHEDULE" > >>>image="IMG-MY_SCHEDULE" action_id="3" > >>>/></WEB_MENU_ITEM><WEB_MENU_ITEM > >>>title="WEB_MENU-HUMAN_RESOURCES"><WEB_MENU_ITEM_USECASE > >>>text="WEB_USE_CASE-EMPLOYEES_AND_CUSTOMERS" > >>>image="IMG-EMPLOYEES_AND_CUSTOMERS" action_id="4" > >>>/><WEB_MENU_ITEM_USECASE text="WEB_USE_CASE-RECORDS" > >>>image="IMG-RECORDS" action_id="5" > >>>/><WEB_MENU_ITEM_USECASE text="WEB_USE_CASE-QUERY" > >>>image="IMG-QUERY" action_id="6" > >>>/></WEB_MENU_ITEM><W > E > >> > >>B_MENU_ITEM > >>title="WEB_MENU-ROOMS_AND_EQUIPMENT"><WEB_MENU_ITEM_USECASE > >>text="WEB_USE_CASE-ROOMS_AND_EQUIPMENT" > >>image="IMG-ROOMS_AND_EQUIPMENT" action_id="7" > >>/></WEB_MENU_ITEM><WEB_MENU_ITEM > >>title="WEB_MENU-HELP" /></WEB_MENU> > >> > >>></item> > >>></values> > >>></ return > > >>></ns1:mintGetMainConfigurationAPIResponse> > >>></SOAP-ENV:Body> > >>></SOAP-ENV:Envelope> > >> > >>However, when the object is deserialized (JavaBeanDeserializer), the XML > >>string looks like this: > >> > >> > >>> ?xml version=1.0 encoding=UTF-8? > >>>WEB_MENU VERSION=1.0WEB_MENU_ITEM title=WEB_MENU-HOMEWEB_MENU_ITEM_USECASE > >>>text=WEB_USE_CASE-WELCOME image=IMG-WELCOME action_id=1 > >>>/WEB_MENU_ITEM_USECASE text=WEB_USE_CASE-MY_RECORDS image=IMG-MY_RECORDS > >>>action_id=2 /WEB_MENU_ITEM_USECASE text=WEB_USE_CASE-MY_SCHEDULE > >>>image=IMG-MY_SCHEDULE action_id=3 //WEB_MENU_ITEMWEB_MENU_ITEM > >>>title=WEB_MENU-HUMAN_RESOURCESWEB_MENU_ITEM_USECASE > >>>text=WEB_USE_CASE-EMPLOYEES_AND_CUSTOMERS > >>>image=IMG-EMPLOYEES_AND_CUSTOMERS action_id=4 /WEB_MENU_ITEM_USECASE > >>>text=WEB_USE_CASE-RECORDS image=IMG-RECORDS action_id=5 > >>>/WEB_MENU_ITEM_USECASE text=WEB_USE_CASE-QUERY image=IMG-QUERY action_id=6 > >>>//WEB_MENU_ITEMWEB_MENU_ITEM > >>>title=WEB_MENU-ROOMS_AND_EQUIPMENTWEB_MENU_ITEM_USECASE > >>>text=WEB_USE_CASE-ROOMS_AND_EQUIPMENT image=IMG-ROOMS_AND_EQUIPMENT > >>>action_id=7 //WEB_MENU_ITEMWEB_MENU_ITEM title=WEB_MENU-HELP //WEB_MENU > >> > >>Somehow SAX refuses to parse this :-) > >> > >>If we just exchange the nightly build soap.jar (no need to recompile) > >>with the prior soap.jar this XML string is correct with angle brackets. > >> > >>Regards > >>Werner > >> > > > > > > > -- > MINT MEDIA INTERACTIVE Software Systems GmbH > Kieler Innovations- und Technologiezentrum > Schauenburgerstrasse 116 > D-24118 Kiel > Germany > phone +49 - 431 - 5606 414 > fax +49 - 431 - 5606 418 > mail [EMAIL PROTECTED] >
