-----Original Message----- From: Farmer, Rod (Contractor) Sent: Tuesday, 11 November 2003 4:54 PM To: '[EMAIL PROTECTED]' Subject: RE: Differentiating <element/> tags
Thanks to both Andy and Simon for their responses. I will look into the implications of using XNI. Cheers Rod -----Original Message----- From: Andy Clark [mailto:[EMAIL PROTECTED] Sent: Tuesday, 11 November 2003 4:47 PM To: [EMAIL PROTECTED] Subject: Re: Differentiating <element/> tags Farmer, Rod (Contractor) wrote: > I was wondering if it is possible to differentiate in Xerces-J > between <element></element> and <element/>? SAX doesn't have any way of differentiating these but XNI does. XNI has two separate methods, "startElement" and "emptyElement", to represent <element> vs. <element/>. You can write your program to receive XNI events straight from the parser configuration of your choice. But realize that this will tie your program code directly to the Xerces implementation. If you want a purely portable app, then be very careful when choosing this route. However, if you do want to use XNI, please refer to the XNI Manual in the documentation. -- Andy Clark * [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]
