[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XMLOut - generating xml from programs

• From: Michael Kay <mike@saxonica.com>
• To: xml-dev@lists.xml.org
• Date: Tue, 23 Aug 2011 18:47:09 +0100

>
>    wax.start("car").text("Prius").end().close();
>
> You'd have:
>
>    altWax.start("car").text("Prius").end("car");
>

Both of these look fine when you're writing literal text. But how does 
it work when you're working your way down a Java hierarchy translating 
it into an XML heirarchy?

Here I think I feel more comfortable with the way I do it today, with an 
XMLStreamWriter:

public void toXML(XMLStreamWriter out) {
   out.startElement("car");
   for (Part part: getParts()) {
       part.toXML(out);
   }
   out.endElement();
}

I agree that the redundant name in the endElement call can be very 
useful when debugging. Make it optional.

Michael Kay
Saxonica

• Follow-Ups:
  • Re: XMLOut - generating xml from programs
    • From: "Pete Cordell" <petexmldev@codalogic.com>

• References:
  • XMLOut - generating xml from programs
    • From: Liam R E Quin <liam@w3.org>
  • Re: XMLOut - generating xml from programs
    • From: Manos Batsis <manos_lists@geekologue.com>
  • Re: XMLOut - generating xml from programs
    • From: Liam R E Quin <liam@w3.org>
  • Re: XMLOut - generating xml from programs
    • From: "Pete Cordell" <petexmldev@codalogic.com>