What is the proposed solution for this?  According to the PDF spec, there 
will never be two objects with the same object number and revision. 
However, this is the real world, not a world of conforming PDF documents, 
so I completely understand that this does occur.  My questions is mainly: 
how do you plan on telling which object is the "right" one, and which one 
should be overwritten?

---- 
Thanks,
Adam





From:
"Thomas Chojecki (JIRA)" <[email protected]>
To:
[email protected]
Date:
06/20/2011 09:17
Subject:
[jira] [Created] (PDFBOX-1042) Wrong XRefStream order while parsing 
incremental updated PDF with XRefStreams



Wrong XRefStream order while parsing incremental updated PDF with 
XRefStreams
-----------------------------------------------------------------------------

                 Key: PDFBOX-1042
                 URL: https://issues.apache.org/jira/browse/PDFBOX-1042
             Project: PDFBox
          Issue Type: Bug
          Components: Parsing
    Affects Versions: 1.5.0
            Reporter: Thomas Chojecki
            Priority: Critical


A PDF can contain two types of XRef-Entries.
Most files use XRefTables for object references.

Web-Optimized (linearized) pdf document uses XRefStreams. This is a 
compresed XRefTable as ObjectStream. The PDFParser parse this objects the 
same way as other objects and put them into an object pool (HashMap). If 
the document was incremental updated, more XRefStreams would be in the pdf 
document and all will be put into the object pool.

The XRefStreamParser begin to parse the XRefStreams and try to gain all 
XRefStream-Object from that pool. The objects returned from the pool 
aren't in the same order as read. This cause that in some cases the older 
Object overwrite the newer one. And this cause that the pdfbox can't find 
the right objects and use the older one instead.

If a user try to parse such a document, he will got an indeterminate 
state. older and newer objects are mixed.

In my case, a document catalog was overwrote by an old one and i can't see 
the changes that was made with the incremental update.

A patch and a sample pdf will come soon.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

 



- FHA 203b; 203k; HECM; VA; USDA; Conventional 
- Warehouse Lines; FHA-Authorized Originators 
- Lending and Servicing in over 45 States 
www.swmc.com   -  www.simplehecmcalculator.com   Visit  www.swmc.com/resources  
 for helpful links on Training, Webinars, Lender Alerts and Submitting 
Conditions  
This email and any content within or attached hereto from Sun West Mortgage 
Company, Inc. is confidential and/or legally privileged. The information is 
intended only for the use of the individual or entity named on this email. If 
you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution or taking any action in reliance on the 
contents of this email information is strictly prohibited, and that the 
documents should be returned to this office immediately by email. Receipt by 
anyone other than the intended recipient is not a waiver of any privilege. 
Please do not include your social security number, account number, or any other 
personal or financial information in the content of the email. Should you have 
any questions, please call (800) 453 7884.  

Reply via email to