Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Ordering in SAX filter

From: Mansour Al Akeel <mansour.alakeel@-----.--->
To: Andrew Welch <andrew.j.welch@-----.--->
Date: 5/18/2008 4:37:00 PM
Andrew, I will look soon into this approach. For now, I am building a 
JDOM document, then do the processing, and when done, I am planning to 
convert the document again to sax event.
I don't have any idea about StAX, but I will look into it. The first 
approach you suggested is fine, except that I don't know how you can 
push events on a stack or a queue. That is what I wanted to do in the 
first place. Can you please kindly give me a small code example showing 
what you mean ? I was going to create the wrapper classes so that I can 
access the event as an object and save them in some data structure.

Andrew Welch wrote:
> 2008/5/18 Mansour Al Akeel <mansour.alakeel@g...>:
>   
>> I need to process some elements in a SAX filter only when a condition
>> occurs. The problem that this condition occurs later, and after all the
>> events for the elements I need to process are fired. For example:
>>     
>
> In the past when I've had this requirement I've either pushed all the
> events onto a stack until the condition comes along, or just parsed
> the document twice.
>
>   
>> I need to know if someone has a better and easier idea ?
>>     
>
> In Java 6 (or StAX in previous versions) you can peek() ahead - check
> the future events before they are fired for real:
>
> http://java.sun.com/javase/6/docs/api/javax/xml/stream/XMLEventReader.html#peek()
>
>
>


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent