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

I am not an xml expert but would it cause problems if every instance of the parent have something like...

<Order></Order>

Aka a null value for "Order"

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
Sent: Wednesday, February 18, 2009 12:57 PM
To: RPG programming on the IBM i / System i
Subject: how to handle option tag when using CGIDEV2 to create xml data

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