 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | SV: [jdom-interest] XMLOutputter changes from b8 to b9 | SV: [jdom-interest] XMLOutputter changes from b8 to b9 2004-01-16 - By Per Norrman
Back
Hi,
Instead of
xmlOutputter.setTextTrim(true);
try
xmlOutputter.setTrimAllWhite(true);
At least your test case says yay!
/pmn
PS. Is it imprudent to ask why those spaces would ever be significant?
Philosophically speaking, what you want is to treat whitespace
differently depending
on the context in which it appears: What if the three spaces in <type>
</type>
is as significant as those in <type> Migration</type>. If that's the
case,
you loose. DS.
> -- --Ursprungligt meddelande-- --
> Fr?n: jdom-interest-admin@(protected)
> [mailto:jdom-interest-admin@(protected)] F?r Beleznay, Dave
> Skickat: den 16 januari 2004 19:46
> Till: Bradley S. Huffman
> Kopia: jdom-interest@(protected)
> ?mne: RE: [jdom-interest] XMLOutputter changes from b8 to b9
>
>
> Really? that is odd, it might be my copy of the jar file, I
> wasn't the one who downloaded it, I'll try getting a new copy
> and trying again. Are you sure that the spaces in the element
> <type> were preserved?
>
> I've attatched my test class here, can you try running it
> when you get a chance?
>
> Thank you.
>
> Cheers,
>
> Dave
>
> > -- --Original Message-- --
> > From: Bradley S. Huffman [mailto:hip@(protected)]
> > Sent: Thursday, January 15, 2004 6:49 PM
> > To: Beleznay, Dave
> > Cc: jdom-interest@(protected)
> > Subject: Re: [jdom-interest] XMLOutputter changes from b8 to b9
> >
> >
> > When I uncomment the following line in your code I get the
> > results you want with B9.
> >
> > //xmlOutputter.setTextTrim(true);
> >
> > Brad
> >
> > "Beleznay, Dave" writes:
> >
> > > Hi There,
> > >
> > > We've recently upgraded from Jdom b8 to b9, and had a few
> errors in
> > > the upgrade process.
> > >
> > > If I have an XML document like so:
> > >
> > > String xml =
> > > "<enterprise>\n"+
> > > "<properties>\n"+
> > > " <datasource>WebCT</datasource>\n"+
> > > " <type> Migration</type>\n"+
> > > " <datetime>2002-06-06T14:59:05</datetime>\n"+
> > > "</properties>\n"+
> > > "</enterprise>\n";
> > >
> > > Where the spaces in front of <datasource> are not
> relevant, but the
> > > spaces inside the elements (e.g. <type>) are relevant (this
> > is just a
> > > fragment of a larger bit of XML, it isn't really the <type>
> > field that
> > > matters here). When I put the document into Jdom, I get different
> > > behaviour between Jdom b8 and b9. I'd like to know the expected
> > > behaviour, and if it doesn't match my desired behaviour,
> > approximately
> > > how I'm supposed to fix my code.
> > >
> > >
> > > Using the string above and the following code in Jdom b8
> I get the
> > > output below.
> > >
> > > SAXBuilder builder = new SAXBuilder();
> > > Document doc = builder.build(new StringReader(xml));
> > >
> > > XMLOutputter xmlOutputter = new
> XMLOutputter("\t", true);
> > > xmlOutputter.setOmitDeclaration(true);
> > > xmlOutputter.setLineSeparator("\n");
> > > //xmlOutputter.setTextTrim(true);
> > > String output = > > > xmlOutputter.outputString(doc
.getRootElement());
> > > System.out.println(output);
> > >
> > > Desired output ( and output received from b8):
> > >
> > > output=
> > >
> >
> "<enterprise>\n\t<properties>\n\t\t<datasource>WebCT</datasource>\n\t\
> > > t<
> > > type>
> > >
> >
> Migration</type>\n\t\t<datetime>2002-06-06T14:59:05</datetime>\n\t</pr
> > > op
> > > erties>\n</enterprise>"
> > >
> > >
> > > When we upgraded to Jdom b9 we were in for a little bit of a
> > > surprise.
> > >
> > > Output from b9 without TextTrim:
> > >
> > > output= "<enterprise>\n\t\n\n\t<properties>\n\t\t\n
> > > \n\t\t<datasource>WebCT</datasource>\n\t\t\n \n\t\t<type>
> > > Migration</type>\n\t\t\n
> > >
> >
> \n\t\t<datetime>2002-06-06T14:59:05</datetime>\n\t\t\n\n\t</properties
> > > >\
> > > n\t\n\n</enterprise>"
> > >
> > > Output from b9 with TextTrim:
> > >
> > > output=
> > >
> >
> "<enterprise>\n\t<properties>\n\t\t<datasource>WebCT</datasource>\n\t\
> > > t<
> > >
> >
> type>Migration</type>\n\t\t<datetime>2002-06-06T14:59:05</datetime>\n\
> > > type>t<
> > > /properties>\n</enterprise>"
> > >
> > > (this is close, but took the spaces out before " Migration" )
> > >
> > > Unfortunately the code farther down the line (not using
> > jdom) which is
> > > analyzing the xml has problems with the string "\n\t\t\n
> > > \n\t\t<datasource>WebCT<datasource>" and interprets the
> value as "
> > > WebCT". I'm not happy with that either, but right now it's
> > easier to
> > > fix the behaviour of Jdom.
> > >
> > > It looks like this was changed XMLOutputter 1.87, and I'm
> trying to
> > > figure out why. I'd like to remove the whitespace outside the
> > > elements, while preserving the whitespace inside. As a temporary
> > > measure I've added the check for currentFormat.newlines
> back to our
> > > skipLeadingWhite method in XMLOutputter, but I'd like a
> > more permanent
> > > solution.
> > >
>
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@(protected)
.com
Earn $52 per hosting referral at Lunarpages.
|
|
|
