OpenSAML user discussion

[Chad La Joie <>]

Paul Hethmon wrote:
> A couple of further things on xml-tooling I've found. One, in the
> build.xml file for the "test" target, at line 94, it specifies the
> jvmarg to pass in the endorsed directories value. It is using an
> attribute of "line" which does not support space characters in the
> pathnames. Using "value" instead seems to clear this up for me.

Fixed.  Thanks for catching this.

> Now that I got it to run the tests, I'm seeing some test failures down
> in org.opensaml.xml.schema. I've got a failure in XSBase64BinaryTest and
> XSStringTest and an error in XSIntegerTest. All of these relate to the
> handling of whitespace in the test values. Meaning for example that "
> 1967" throws an exception on parseInt. The other two are both expecting
> their test values to be space padded (before and after). Is this an
> error in the test setup? Or am I using the wrong version of a library
> perhaps?

Fixed.

> In the developer docs, it states to put copies of Xerces and Xalan in
> the endorsed directory (done), but doesn't particularly say which
> versions. I've just grabbed the latest versions as of today (xerces
> 2.9.0, xalan 2.7.0).

The Xerces and Xalan that we use for testing and running the code are in 
the thirdparty-lib directory.  I try to make sure we're always on the 
latest one but that older ones will work too.  The basic, underlying, 
requirement is JAXP 1.3 from some provider other than Sun (which we know 
to be pretty broken).

> I guess one other thing. On the junit line (93), haltonfailure is set to
> true which ends up halting the test as intended, but does not leave me
> any information on the command line. Setting that to false gives me the
> unit test output in the doc directory which outlines the above errors.
> Btw, my build environment is WinXP with JDK 1.5.0_06.

Fixed.

--
Chad La Joie             2052-C Harris Bldg
OIS-Middleware           202.687.0124