You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by Elliot Metsger <em...@jhu.edu> on 2006/08/05 02:24:52 UTC
Re: Castor and XML namespaces (was Moving toward a Pluto 1.1 beta
releas
CDoremus@hannaford.com wrote:
<snip, snip>
> Sorry, but I don't have a clue about the
> org.exolab.castor.parser.namespaces parameter and could not figure out
> from the SVN repository where it came from.
Neither could I.
Here are the default values, set by the castor.properties file contained
in the castor jar:
Overridden value in the portal subproject (default value)
=========================================================
org.exolab.castor.parser.validation=false (false by default in jar)
org.exolab.castor.parser.namespaces=true (false by default in jar)
org.exolab.castor.indent=true (commented out in jar, I presume that the
default is false)
org.exolab.castor.debug=false (false by default in jar)
So someone chose to explicitly override the default value in
org.exolab.castor.parser.namespaces property. But I can't tell why.
> When you set the property to
> false, do any of the testsuite tests fail?
All tests in the testsuite portlet pass except for Portal Info Test -
Portal info: pluto-driver/1.0.1. Expected: pluto-driver/1.0.1-SNAPSHOT
(which is benign I think, since I'm building from source).
So... not sure where that leaves us. I'm pretty confident that
switching the namespaces property value to false is ok. I am also
adding some more unit tests to the descriptors sub-project.
I'll commit my patch (PLUTO-216) and the additional/refactored unit
tests for the descriptors project. I can wait a little while longer on
the castor.properties file change in case others would like to chime in.
Thanks!
Elliot