Re: how to handle option tag when using CGIDEV2 to create xml data

Hi Lim,

I would put all the xml code in the Template and only update the variables
in your rpg pgm for 2 reasons:

1) Visibility, it is not easy to have an overview when the layout is in
different source files
2) Once the variables are in place, IMHO it is easier to change just the
xml template rather than changing and recompiling the program.


I am not familiar with xsd so the template will not match your schema, but
I hope it will give you an idea ...


/$myXMLSec
<PaymentInformationType>
< /%PaymentChoice%/ >
<BillShipper>
< /%Payment%/ > /%CCAct%/ </ /%Payment%/ >
</BillShipperType>
</ /%PaymentChoice%/ >
</PaymentInformationType>




Select ;
When order.paymentType = 'PRP';
updHtmlVar('PaymentChoice' :'Prepaid' ) ;
When order.paymentType = 'BTP';
updHtmlVar('PaymentChoice' :'BillThirdParty' ) ;
When order.paymentType = 'FC';
updHtmlVar('PaymentChoice' :'FreightCollect' ) ;
When order.paymentType = 'CB';
updHtmlVar('PaymentChoice' :'ConsigneeBilled' ) ;
Endsl ;

Select ;
When order.payment = 'SA';
updHtmlVar('Payment' :'AccountNumber' ) ;
updHtmlVar('CCAct' : ShipperAct# ) ;
When order.payment = 'CC';
updHtmlVar('Payment' :'CreditCard' ) ;
updHtmlVar('CCAct' : CreditCard# ) ;
Endsl ;

Wrtsection('myXMLSec') ;


If the definition changes for each PaymentType, you'd probably need a
section per PaymentType...

HTH

Have a Nice Day
Wim



"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
18/02/2009 22:46
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
<rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: how to handle option tag when using CGIDEV2 to create xml data






Just to clarify my question a bit.

Here is the portion of xsd that I'm dealing:
<xsd:complexType name="PaymentInformationType">
<xsd:choice>
<xsd:element
name="Prepaid" type="PrepaidType"
minOccurs="0"/>
<xsd:element
name="BillThirdParty"
type="BillThirdPartyType" minOccurs="0"/>
<xsd:element
name="FreightCollect"
type="FreightCollectType" minOccurs="0"/>
<xsd:element
name="ConsigneeBilled"
type="xsd:string" minOccurs="0"/>
</xsd:choice>
</xsd:complexType>

In my RPG program, depending on the shipment method selected on the
order, it will determine which child element to used when creating the
PaymentInformation tag. My question is how should I create the template
to handle creating above xml using tools in CGIDEV2?

If I create the template as below:
<PaymentInformation>
/%paymentType%/ ==>
</PaymentInformation>


I would have to code it like below in RPG (Not pretty):
If order.paymentType = 'PRP';
updHtmlVar('paymentType'
:'<Prepaid>'
'<BillShipper>' +
'<AccountNumber>' +
%trim(shipperAct#) +
'</AccountNumber>' +
'</BillShipper>' +
:'</Prepaid>'
. . .
. . .


wrtSection('myXMLSec');




Note: here is the prepaidType definition:

<xsd:complexType name="PrepaidType">
<xsd:sequence>
<xsd:element
name="BillShipper"
type="BillShipperType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="BillShipperType">
<xsd:choice>
<xsd:element
name="AccountNumber"
type="xsd:string" minOccurs="0"/>
<xsd:element
name="CreditCard"
type="CreditCardType" minOccurs="0"/>
</xsd:choice>
</xsd:complexType>


"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote in message
news:<mailman.4337.1234979882.26163.rpg400-l@xxxxxxxxxxxx>...
How does one normally handle optional xml tag when using CGIDEV2 to
create the xml data?

should I do something like below?

Template:
/$myXMLSec
<Order>
/%myOptTag%/
</Order>



RPG code:
updHtmlVar('myOptTag' :'<MyOptTag>blah blah blah</MyOptTag>');
wrtSection('myXMLSec');




Or is there a better way of handling this?

thanks
----------