[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Special String in XML file.
Hi Alan,
What you have is an XML document that's the "payload" of a SOAP message.
Remember, SOAP can be used to pass any type of data... you can pass
normal character strings, obviously, and you can also pass images,
sound, movies, PDF documents, etc. ... and yes, you can pass an XML
document.
SOAP is intended to represent a call to a routine.
So if you had this:
CALL MYROUTINE( parm1, parm2 )
Then the soap message might look like this:
<Envelope>
<Body>
<MyRoutineInput>
<parm1>..contents of parm1...</parm1>
<parm2>..contents of parm2...</parm2>
</MyRoutineInput>
<Body>
</Envelope>
But if you were doing this in Java, PHP, C#, or any other tool that
handles the SOAP processing for you, you'd never see this SOAP message.
All you'd know is that you called MYROUTINE and passed the two parameters.
Well, what would happen if you did this?
parm1 = '<myXml>blah</myXml>';
CALL MYROUTINE( parm1, parm2 )
Remember, most web service consumers don't even know the SOAP message
exists... but they want to pass XML data as a parameter to a routine...
So what happens in the SOAP message that occurs under the covers?
<Envelope>
<Body>
<MyRoutineInput>
<parm1><xmXML>blah</myXml></parm1>
<parm2>..contents of parm2...</parm2>
</MyRoutineInput>
<Body>
</Envelope>
So this is a fairly common thing... the XML is being passed as a
parameter.
The caller certainly expects the XML to be passed as a string to the
routine it calls. It does NOT expect the SOAP parser (which is under the
covers, and invisible) to parse the contents of myXML -- that makes no
sense!
I guess you could say that the problem with HTTPAPI as a web service
tool is that it's NOT A WEB SERVICE TOOL. It's an HTTP tool. It passes
data over the network, but it does nothing to take care of the SOAP
message. Personally, I've not found it hard to handle soap messages by
hand -- and the way HTTPAPI handles it is MUCH more versatile than other
tools (like IWS client, for example.)
So anyway, to answer your question: You're asking the wrong question.
You don't want Expat to treat the < and > (etc) as < and >. You
don't WANT it to parse that as part of the SOAP message.
But, you DO need to parse the XML twice! You need to parse the SOAP
message to get the contents of the parameters (i.e. parm1 in my example,
or 'operationResult' in your example). The data in the
'operationResult' will be the XML string that was passed to you as a
parameter, and all of the <, >, etc should be decoded for you (but
unparsed) when you receive the contents of operationResult
NOW you've got the contents of your parameter, so you you can parse the
XML that's inside of it (as a separate step). To do that, you can use
RPG's XML-INTO or XML-SAX opcodes, or you can use HTTPAPI's
http_parse_xml_stmf or http_parse_xml_string, or you can call Expat
directly... whatever you prefer.
An example of this type of processing with HTTPAPI is here:
http://www.scottklement.com/httpapi/bankrout.txt
On 4/28/2011 6:48 PM, Alan Campin wrote:
>
> I have a XML document that I am receiving that a package that is
> inside a soap envelope.
>
>
> Using the EXAMPLE17 that is included in the HTTP downloads I can see
> how to process and extract the inside package but it has strings
> instead of special characters.
>
>
> It has
>
>
> < =<
>
> > =>
>
> " = "
>
>
> Is there a way to tell Expat using the HTTP api's to recognize these
> strings as the symbols or does it just recognize them as such (PC
> editors don't seem to) or am I going to have to read the file through
> and write back with symbols?
>
>
> Thanks for the help.
>
>
> Operation Result is the inside package.
>
>
> <?xml version='1.0' encoding='UTF-8'?>
>
> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/";>
>
> <S:Body>
>
> <ns2:ServiceResponse
> xmlns:ns2="http://stem.startrak.com/gw/";>
>
> <status>0</status>
>
>
> <sessionId>-5701ce8f:12f9516f837:-396d</sessionId>
>
>
> <operationResult><?xml version="1.0"
>
>
> encoding="UTF-8" standalone="yes"?>
>
>
> <ns2:StMessage
>
>
> xmlns:ns2="http://ramp.startrak.com/RAMP.1.0.0/">
>
>
> <status>0</status>
>
>
> <messageTypes>REEFER_STATUS</messageTypes>
>
>
> <messageCount>1</messageCount>
>
>
> <queueStatus>MORE_DATA</queueStatus>
>
>
> <ReeferStatusMessage>
>
>
> <asset>
>
>
> <assetName>ENGZ30280</assetName>
>
>
> <assetState>1</assetState>
>
>
> <config>
>
>
> <microConfig>
>
>
> <microManufacturer>1</microManufacturer>
>
>
> <microModel>3</microModel>
>
>
> <microType>1</microType>
>
>
> <compartmentCount>1</compartmentCount>
>
>
> </microConfig>
>
>
> <rtConfig>
>
>
> <unitSerialNumber>GCTH001730</unitSerialNumber>
>
>
> <unitFirmwareRelease>W0096</unitFirmwareRelease>
>
>
> <unitFirmwareVersion>3.52</unitFirmwareVersion>
>
>
> </rtConfig>
>
>
> </config>
>
>
> </asset>
>
>
> <reeferStatus>
>
>
> <alerts>
>
>
> <batteryAlert>0</batteryAlert>
>
>
> <fuelAlert>0</fuelAlert>
>
>
> <pmAlert>1</pmAlert>
>
>
> <temp1Alert>0</temp1Alert>
>
>
> <temp2Alert>0</temp2Alert>
>
>
> <temp3Alert>0</temp3Alert>
>
>
> </alerts>
>
>
> <ambientTemp>89.6</ambientTemp>
>
>
> <batteryVoltage>12.5</batteryVoltage>
>
>
> <compartmentStatus>
>
>
> <number>1</number>
>
>
> <setpointTemp>-10.0</setpointTemp>
>
>
> </compartmentStatus>
>
>
> <door1Status>-1</door1Status>
>
>
> <door2Status>0</door2Status>
>
>
> <engineHours>13505</engineHours>
>
>
> <event>
>
>
> <eventCode>35044</eventCode>
>
>
> <eventType>0</eventType>
>
>
> </event>
>
>
> <fuel>74.0</fuel>
>
>
> <gps>
>
>
> <city>WARREN</city>
>
>
> <geofence>
>
>
> <geofenceId>0</geofenceId>
>
>
> </geofence>
>
>
> <latitude>41.17205858</latitude>
>
>
> <longitude>-80.80940008</longitude>
>
>
> <state>OH</state>
>
>
> </gps>
>
>
> <hookStatus>-1</hookStatus>
>
>
> <intelliset>
>
>
> <intellisetCode>-1</intellisetCode>
>
>
> <intellisetState>1</intellisetState>
>
>
> </intelliset>
>
>
> <messageStamp>2011-04-27T13:54:59.000Z</messageStamp>
>
>
> <reeferAlarmStatus>0</reeferAlarmStatus>
>
>
> <reeferMoveStatus>1</reeferMoveStatus>
>
>
> <serviceState>3</serviceState>
>
>
> <standbyHours>0</standbyHours>
>
>
> <switchOnHours>23475</switchOnHours>
>
>
> <reeferPower>0</reeferPower>
>
>
> </reeferStatus>
>
>
> <systemStatus>
>
>
> <correlationId>1001</correlationId>
>
>
> <isRedelivered>false</isRedelivered>
>
>
> <numberOfRetries>1</numberOfRetries>
>
>
> <queuedStamp>2011-04-27T14:00:46.292Z</queuedStamp>
>
>
> </systemStatus>
>
>
> </ReeferStatusMessage>
>
>
> </ns2:StMessage></operationResult>
>
> </ns2:ServiceResponse>
>
> </S:Body>
>
> </S:Envelope>
>
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------