+1 "PS Think that FilteringTrigger must be renamed to SAXDocumentTrigger (SAXTrigger)"

For those who are interested we have been testing this successfully this week. There are somethings that other developers should know if they are going to use the functionality:

  1. The SAX parser makes two passes over the stream, one with isValidating() set to true, and the second with isValidating() set to false. On the second pass you should not be throwing any exceptions, or allowing NPE's because this is when the stream is being stored.
  2. The second pass is the only one which can actually modify the SAX stream, if you modify the stream in the first pass, but not the second, you will not see your changes in the resulting stored file.
  3. Make sure you always call the super method in your SAX methods to ensure that you do not unintentionally omit information from the stream.

Using this process we have been able to significantly increase the efficiency of our document processing on storage. More people testing would be greatly appreciated.



On Sat, Jan 25, 2014 at 4:28 AM, Dmitriy Shabanov <shabanovd@gmail.com> wrote:

I did redesign & fix document sax events trigger. It's here for testing https://github.com/shabanovd/exist/tree/RC9

Ready to discuss if it make problems for anyone and waiting for possitive responcies too -)

As sson as I get OKs I'll send pull request. 

Dmitriy Shabanov

PS Think that FilteringTrigger must be renamed to SAXDocumentTrigger (SAXTrigger)

CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
Exist-development mailing list

Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
(585) 348 7399

This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.