ok, but if you specify exactly the legal children of HourList and don't include
whitespace i.e. like (dtd style)
<!ELEMENT HourList Hour*>
<!ELEMENT Hour EMPTY>
or something like that
then ignoreWhitespace will work like you want it to and not just for the
validating parsers...
(i think) :)
john
"Dalia, Keith A - TOS-DITT1" wrote:
> Thanks John, My editor saves my xml files in canonical form. Xerces treats
> the tabs or whatever they are as Nodes.
> I simply check NodeType and just get the Element Nodes. And everything
> works. I got started on XML validation late in the game and have never used
> DTD's.
>
> Keith
>
> -----Original Message-----
> From: John J. Berkenpas [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 03, 2001 12:14 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Ignorable Whitespace
>
> ok bear with me because i'm not at all familiar with schemas. what does the
> child list (or whatever the equivelent is in schemas) say is legal for
> HoursList ? im thinking that whatever it is somehow allows whitespace (
> (#PCDATA) maybe?) and you're getting all the end of lines. maybe thats
> obvious
> and i should just shut-up? I struggled with the same kind of problem a few
> months back
>
> "Dalia, Keith A - TOS-DITT1" wrote:
>
> > Maybe I'm misunderstanding Whitespace. Please help resolve this
> > mis-understanding. I'm using xml schema and I have three options for
> > whitespace: collapse, replace, and preserve.
> >
> >
> > <Account name = "Maximum Gen VAR (GVC+)">
> > Is the space "Maximum" and "Gen" whitespace?
> >
> > OR my xml editor (XML Instance) seems to format my xml files.
> >
> > LIKE:
> >
> > <HourList>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour xsi:null = "true"/>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour>0</Hour>
> > <Hour xsi:null = "true"/>
> > </HourList>
> > When I parse this with Xerces the HourList Node has 49 children, but it
> > really only has 24.
> > It that also whitespace?
> >
> > Thanks Keith
> >
> > -----Original Message-----
> > From: John J. Berkenpas [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 02, 2001 1:08 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Ignorable Whitespace
> >
> > if your dtd allows whitespace in a node then it is NOT ignorable even
> though
> > it
> > seems so to you. i.e. if its #text then whitespace is ok and the parser
> > doesn't
> > ignore it. it can't know that you don't need it.
> >
> > "Dalia, Keith A - TOS-DITT1" wrote:
> >
> > > I don't want white space included in my tree:
> > >
> > > I use parser.setIncludeIgnorableWhitespace(false);
> > >
> > > but text nodes that can be considered "ignorable whitespace" still
> appear
> > in
> > > the dom tree.
> > > What am I doing wrong.
> > >
> > > DOMParser parser = new DOMParser();
> > >
> > > try
> > > {
> > >
> //parser.setFeature("http://xml.org/sax/features/validation";,
> > > true);
> > > parser.setIncludeIgnorableWhitespace(false);
> > > parser.parse("gi.xml");
> > >
> > > }
> > > catch (java.io.IOException ioe)
> > > {
> > > System.out.println(ioe.toString());
> > > }
> > >
> > > catch (SAXNotRecognizedException snre)
> > > {
> > > snre.printStackTrace();
> > > }
> > > catch (SAXException saxe)
> > > {
> > > saxe.printStackTrace();
> > > }
> > >
> > >
> > > Document document = parser.getDocument();
> > >
> > >
> > > TIA, Keith
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
