[jira] [Commented] (PDFBOX-2318) NPE in new DomXmpParser when no type is found

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PDFBOX-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168649#comment-14168649 ] 

ASF subversion and git services commented on PDFBOX-2318:
---------------------------------------------------------

Commit 1631175 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1631175 ]

PDFBOX-2318: avoid NPE when parsing a XMP-file containing an undefined type as proposed by Jeremy Anderson

> NPE in new DomXmpParser when no type is found
> ---------------------------------------------
>
>                 Key: PDFBOX-2318
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-2318
>             Project: PDFBox
>          Issue Type: Bug
>          Components: XmpBox
>    Affects Versions: 2.0.0
>            Reporter: Jeremy Anderson
>            Assignee: Andreas Lehmkühler
>              Labels: patch
>             Fix For: 2.0.0
>
>         Attachments: PDFBOX-2318.patch, jsr170-1.0.pdf
>
>
> Discovered this bug while trying to sync both TIKA and PDFBOX to their current SNAPSHOT builds.
> Issue came to light when running Tika's JpegParserTest.testJPEGEmptyEXIFDateTime() junit test case since the test file contains the following property photoshop:LegacyIPTCDigest which is a non defined property in the PhotoshopSchema.
> This causes a null Type to be created in DomXmpParser.parseDescriptionRoot().  The solution in my patch is to default to text for any undefined types.  It may be beneficial to also log a warning about such types so that the schema files can be properly amended.  (Currently the LegacyIPTCDigest has not been added to the Schema in this patch)
> Relates to work done via Tika in TIKA-1285



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)