[
https://issues.apache.org/jira/browse/OODT-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219325#comment-13219325
]
Chris A. Mattmann edited comment on OODT-395 at 2/29/12 4:25 PM:
-----------------------------------------------------------------
Hey guys, yeah I think there are two issues here.
First, the issue of Ricky's small patch to simply make SerializableMetadata
generate metadata files that simply match the way we normally generate them
elsewhere in the system. +1 to that, small, incremental patch, where Ricky has
done the work and it doesn't hurt anything and makes us more consistent. I also
think it's good because it's a small incremental, and reversible change.
Second, Paul has raised a good XML schema/XSD practice in general that we might
want to look at following, that has broader implications across the rest of the
components and ecosystem. Let's not get hung up discussing that here. If Paul
or Brian or myself or anyone else want to go down that road, we can do so, in a
separate thread. My guess is that we won't have the time or it'll get hung up
somewhere, and if so, great, if not, great too. But we shouldn't let it hang up
this change IMHO, since it's a small, good, incremental step.
was (Author: chrismattmann):
Hey guys, yeah I think there are too issues here.
First, the issue of Ricky's small patch to simply make SerializableMetadata
generate metadata files that simply match the way we normally generate them
elsewhere in the system. +1 to that, small, incremental patch, where Ricky has
done the work and it doesn't hurt anything and makes us more consistent. I also
think it's good because it's a small incremental, and reversible change.
Second, Paul has raised a good XML schema/XSD practice in general that we might
want to look at following, that has broader implications across the rest of the
components and ecosystem. Let's not get hung up discussing that here. If Paul
or Brian or myself or anyone else want to go down that road, we can do so, in a
separate thread. My guess is that we won't have the time or it'll get hung up
somewhere, and if so, great, if not, great too. But we shouldn't let it hang up
this change IMHO, since it's a small, good, incremental step.
> SerializableMetadata.toXml() doesn't set namespace on root element
> ------------------------------------------------------------------
>
> Key: OODT-395
> URL: https://issues.apache.org/jira/browse/OODT-395
> Project: OODT
> Issue Type: Bug
> Components: metadata container
> Affects Versions: 0.4
> Reporter: Ricky Nguyen
> Fix For: 0.4
>
> Attachments: rickdn.oodt-395.patch
>
>
> This issue becomes apparent when using
> o.a.o.cas.pge.writers.xslt.XslTransformWriter in the <dynInputFile> element
> of a PGE config xml. If you use the identity xsl transform
> (http://en.wikipedia.org/wiki/Identity_transform#Using_XSLT):
> {code}
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
> <xsl:template match="@*|node()">
> <xsl:copy>
> <xsl:apply-templates select="@*|node()"/>
> </xsl:copy>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> Then the root element is NOT part of the "cas" namespace:
> {code}
> <metadata xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas";>
> ...
> </metadata>
> {code}
> Whereas the serialized form of metadata (when written to a File or
> OutputStream) DOES use the "cas" namespace:
> {code}
> <cas:metadata xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas";>
> ...
> </cas:metadata>
> {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
