Mailing-List: contact commits-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@oodt.apache.org
Date: Sat, 7 May 2011 22:34:03 +0000 (UTC)
From: "Chris A. Mattmann (JIRA)" <jira@apache.org>
To: commits@oodt.apache.org
Message-ID: 
 <130785043.30612.1304807643227.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (OODT-191) PushPull FileRetrievalSystem NPE if
 mime comment for type doesn't include ampersand
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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.2, 0.1-incubating
         Environment: while testing on SNOW and on NEON
            Reporter: Chris A. Mattmann
            Assignee: Chris A. Mattmann
            Priority: Blocker
             Fix For: 0.3


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