You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/06/05 03:35:50 UTC

[jira] [Updated] (OODT-191) PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand

     [ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-191:
-----------------------------------

    Fix Version/s:     (was: 0.3)
                   0.4

> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
>                 Key: OODT-191
>                 URL: https://issues.apache.org/jira/browse/OODT-191
>             Project: OODT
>          Issue Type: Bug
>          Components: push pull framework
>    Affects Versions: 0.1-incubating, 0.2
>         Environment: while testing on SNOW and on NEON
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>            Priority: Blocker
>              Labels: NPE, file, pull, push, retrieval, system
>             Fix For: 0.4
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.

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