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

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

    Fix Version/s: 0.4
         Assignee: Ross Laidlaw
    
> Allow XML namespaces to be defined in the RSS configuration file for the CAS 
> REST service ('fmprod' webapp)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: OODT-458
>                 URL: https://issues.apache.org/jira/browse/OODT-458
>             Project: OODT
>          Issue Type: Improvement
>          Components: file manager
>            Reporter: Ross Laidlaw
>            Assignee: Ross Laidlaw
>            Priority: Minor
>             Fix For: 0.4
>
>
> Update the CAS REST RSS service to allow namespaces to be defined in the RSS 
> configuration file.
> Tag format for the RSS configuration file suggested by Paul Ramirez on 
> [OODT-449|https://issues.apache.org/jira/browse/OODT-449].  Examples shown 
> below:
> {code}
> <namespace prefix="geo" uri="http://www.w3.org/2003/01/geo/wgs84_pos#"; />
> <namespace prefix="georss" uri="http://www.georss.org/georss"; />
> <namespace prefix="gml" uri="http://www.opengis.net/gml"; />
> {code}
> Two RSS java classes have hard-coded 'cas' namespace definitions: 
> RSSProductServlet and RSSProductTransferServlet.  These classes both use a 
> hashmap constant 'NS_MAP' to store namespaces and write them to the RSS 
> output.  With configurable namespaces, the 'cas' namespace definition could 
> also be moved to the RSS config and picked up by the ProductServlet and 
> TransferServlet from there instead of having hard-coded definitions:
> {code}
> <namespace prefix="cas" uri="http://oodt.apache.org/components/cas"; />
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to