[
https://issues.apache.org/jira/browse/OODT-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263912#comment-13263912
]
Ross Laidlaw commented on OODT-449:
-----------------------------------
I also experimented with adding the following code for the rss element in the
RSSProductServlet class:
{code}
XMLUtils.addAttribute(doc, rss, "xmlns:geo",
"http://www.w3.org/2003/01/geo/wgs84_pos#";);
XMLUtils.addAttribute(doc, rss, "xmlns:georss", "http://www.georss.org/georss";);
XMLUtils.addAttribute(doc, rss, "xmlns:gml", "http://www.opengis.net/gml";);
{code}
This resulted in adding the namespace definitions to the 'rss' tag of the
output, for example as follows:
{code}
<rss xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#";
xmlns:georss="http://www.georss.org/georss";
xmlns:gml="http://www.opengis.net/gml";
version="2.0">
{code}
But this information would then be hard-coded and consequently all RSS outputs
from fmprod would contain these namespaces, even if they did not concern files
from the LocationAwareProduct family and did not have location meta-data. So
perhaps this is not the ideal solution.
> Create a default GeoRSS configuration file for the fmprod web application
> -------------------------------------------------------------------------
>
> Key: OODT-449
> URL: https://issues.apache.org/jira/browse/OODT-449
> Project: OODT
> Issue Type: Sub-task
> Components: file manager
> Reporter: Ross Laidlaw
> Labels: gsoc2012
> Fix For: 0.5
>
>
> Create a default GeoRSS configuration file for the fmprod web application of
> the File Manager component.
> The GeoRSS configuration file will contain all of the information from the
> default RSS configuration file. In addition, it will also contain
> definitions for latitude and longitude GeoRSS XML tags.
> Name the file 'georss-config.xml' and add the file to
> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources
--
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
