Return-Path: 
 <user-return-502-apmail-oodt-user-archive=oodt.apache.org@oodt.apache.org>
X-Original-To: apmail-oodt-user-archive@minotaur.apache.org
Delivered-To: apmail-oodt-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9B33CD15F
	for <apmail-oodt-user-archive@minotaur.apache.org>;
 Wed,  1 Aug 2012 15:29:21 +0000 (UTC)
Received: (qmail 54461 invoked by uid 500); 1 Aug 2012 15:29:21 -0000
Delivered-To: apmail-oodt-user-archive@oodt.apache.org
Received: (qmail 54435 invoked by uid 500); 1 Aug 2012 15:29:21 -0000
Mailing-List: contact user-help@oodt.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@oodt.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@oodt.apache.org>
List-Post: <mailto:user@oodt.apache.org>
List-Id: <user.oodt.apache.org>
Reply-To: user@oodt.apache.org
Delivered-To: mailing list user@oodt.apache.org
Received: (qmail 54414 invoked by uid 99); 1 Aug 2012 15:29:21 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 15:29:21 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of yunh.kang@gmail.com designates
 209.85.214.171 as permitted sender)
Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com)
 (209.85.214.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 15:29:13 +0000
Received: by obqv19 with SMTP id v19so29674680obq.16
        for <multiple recipients>; Wed, 01 Aug 2012 08:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:cc:content-type;
        bh=t5GEHo0r7bjCqm79Zvw/60JBTJSkM7r222d5CX+oeyU=;
        b=ZPnu67yuRMTl8OEhIGtZOuyXosgZ/snTlyhBLB/Q4FgRp9LrAbGgPt53CLpqdk/Tle
         yz0kKwa8wnA+vF411RIcHa3PvCWtJGB611NPaiCyJCGgRypxrPpPUz6erhaiHaKubKkf
         X4DPNwDArwP/wLtYiwKbHKBimX5ZaTpaTgO0gOHBBc6asEGi+bi5YRAS6iH07xmDTXN9
         o5O/Qi+Qk9b6C4NQiRir/rlMuaYYVkYtJC93LwefubcYkiNuMx/BuZ4M+h4qrR30mqyj
         L4s8J9x/7Hw+21kPfGKjwpz6tjSvg8plgdxQbAKGtdY7VAFHq2lh8PHZRM9uyQ4mrGP1
         mlXg==
MIME-Version: 1.0
Received: by 10.182.73.65 with SMTP id j1mr8294104obv.42.1343834932493; Wed,
 01 Aug 2012 08:28:52 -0700 (PDT)
Received: by 10.182.118.99 with HTTP; Wed, 1 Aug 2012 08:28:52 -0700 (PDT)
Date: Thu, 2 Aug 2012 00:28:52 +0900
Message-ID: 
 <CAH=8jEChJAYyE+ggaNgKbm=Pg5m8Ti_jfkMZfwyterBLe9n2xw@mail.gmail.com>
Subject: Question about metadata specification for Filemgr and Pushpull
From: YunHee Kang <yunh.kang@gmail.com>
To: "Mattmann, Chris A (388J)" <chris.a.mattmann@jpl.nasa.gov>,
 Brian Foster <holenoter@mac.com>
Cc: user@oodt.apache.org, "<dev@oodt.apache.org>" <dev@oodt.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi Chris and Brian,

I am reading source codes for handling "Catalog exception" related the
runtime error described below.
org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
Failure writing request
    at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.hasProduct(XmlRpcFileManagerClient.java:606)
    at org.apache.oodt.cas.filemgr.ingest.StdIngester.hasProduct(StdIngester.java:284)
    at org.apache.oodt.cas.pushpull.retrievalsystem.FileRetrievalSystem.isAlreadyInDatabase(FileRetrievalSystem.java:254)
    at org.apache.oodt.cas.pushpull.retrievalsystem.FileRetrievalSystem.addToDownloadQueue(FileRetrievalSystem.java:463)
    at org.apache.oodt.cas.pushpull.retrievalmethod.RemoteCrawler.processPropFile(RemoteCrawler.java:138)
    at org.apache.oodt.cas.pushpull.retrievalsystem.RetrievalSetup.retrieveFiles(RetrievalSetup.java:109)
    at org.apache.oodt.cas.pushpull.daemon.Daemon$1.run(Daemon.java:218)
    at java.lang.Thread.run(Thread.java:662)

I think that the exception was caused by the wrong value of the
parameter productName of the method  hasProduct() in the following
codelet of  XmlRpcFileManagerClient.java:
at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.hasProduct(XmlRpcFileManagerClient.java:606)
public boolean hasProduct(String productName) throws CatalogException {
       Vector<Object> argList = new Vector<Object>();
       argList.add(productName);

       boolean hasProduct = false;

       try {
           hasProduct = ((Boolean) client.execute("filemgr.hasProduct",
                   argList)).booleanValue();
       } catch (XmlRpcException e) {
           throw new CatalogException(e.getMessage());
       } catch (IOException e) {
           throw new CatalogException(e.getMessage());
       }
       return hasProduct;
   }

I inspected that  the element  "mine-type" described below was added
in the file mimestypes.xml  that is  one of pushpull property files.
 <mime-type type="product/tes">
           <_comment>ProductType=MyTesProductType</_comment>
          <glob
pattern="TES-Aura_L2-CO2-Nadir_r\d{10}\w{2}\d{2}\w\d{2}\.he5"
isregex="true"/>
        </mime-type>

I would like to know what the element "mine-type" means.
I am wondering how I can check the value of productName in the
properties of Filemgr and Pushpull.

I am sorry to bother you again.

Thanks,
Yunhee