• From: Mansour Al Akeel <mansour.alakeel@g...>
• To: Andrew Welch <andrew.j.welch@g...>
• Date: Sun, 18 May 2008 13:36:28 -0300

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()
>
>
>   

• References:
  • Ordering in SAX filter
    • From: Mansour Al Akeel <mansour.alakeel@g...>
  • Re: Ordering in SAX filter
    • From: "Andrew Welch" <andrew.j.welch@g...>