Hi Benson,

I'm looking into it, but it's not a job function for me so it'll have to be 
an out-of-hours thing.  I hope somebody else beats me to the punch with an 
answer.

Cheers,
Paul.

-----Original Message-----
From:   Benson Cheng [SMTP:[EMAIL PROTECTED]
Sent:   Saturday, August 23, 2003 1:52 AM
To:     [EMAIL PROTECTED]
Subject:        RE: Empty tag handling question

Yes, the same problem exists in version 2.5.0 as well.

thanks,
Benson.

-----Original Message-----
From: Jeffery B. Rancier [mailto:[EMAIL PROTECTED]
Sent: Friday, August 22, 2003 5:33 AM
To: [EMAIL PROTECTED]
Subject: Re: Empty tag handling question


"Benson Cheng" <[EMAIL PROTECTED]> writes:

The first thing I'd do (if possible) is to upgrade to 2.5.0 and try to
duplicate the alleged problem.

> Hi All,
>
> I found that Xerces handles <EmptyTag></EmptyTag> and <EmptyTag/> 
differently when parse with the schema validation.  Assume this <EmptyTag> 
failed the validation,
>
> For <EmptyTag></EmptyTag> case, Xerces calls the handler in the following 
sequence:
> startElement
> error
> endElement
>
> But for <EmptyTag/> case, Xerces calls the handler in the following 
sequence:
> error
> startElement
> endElement
>
> I am not sure the later case is correct or not.  Since my app builds the 
element path when there are errors, the later case reports the wrong 
element path (the parent element).  Is this a bug?  BTW, I am using Xerces 
version 2.4.0.
>
> thanks,
> Benson.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

--
Thanks,
Jeff

,----
| Jeffery B. Rancier
|
| Softechnics
| a METTLER TOLEDO company
`----


---------------------------------------------------------------------
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]

Reply via email to