OpenSAML user discussion

[Chad La Joie <>]

Anil Saldhana wrote:
> The issues are:
> a) Need to clear the tests to get the archives.

This will remain.  The archives are not valid builds of the software 
until they at least pass the unit tests.  Unfortunately we don't yet 
have enough tests to ensure that the code is correct even when it does 
pass them, but I simply don't currently have the time to write 
exhaustive unit tests.

> b) Use of <if> ant task (which is contrib and not standard IMO)

If you use the build scripts that ship with the applications this works 
fine.  If you choose not to use that build environment you'll need to 
set your alternative environment up appropriately.

> c) There is no real relationship between the three modules when using 
> ant command line.

When we make releases of the library all the jars are bundled together 
in the OpenSAML distribution.  During development though we need to keep 
all the libraries (and they are three separate libraries, one building 
on top of the other) in sync.  It is simply not feasible to continually 
rebuild the libs and recommit them to the repository every time we make 
a change.

> OpenSAML 1 was a breeze in checkout, build and test.
>
> I understand that opensaml2 is still in development. But is it possible 
> to get the workspaces to build with little setup
> for a new comer?

The current setup, quite honestly, is not meant to serve the needs of 
people who wish to use the code in their applications.  Right now, as 
the libraries are still under heavy development, the projects are setup 
to make things easier for OpenSAML developers.  That's the current, 
intended, audience.

Each release of OpenSAML 2 that we've made so far has built in exactly 
the same way as OpenSAML 1 (i.e. simply run ./ant).

> An issue I see building the XMLTooling project is that the "test" target 
> is choking
>
> ===================
> I am using JDK5.  Do I need to do endorsement specifically or the system 
> property ${ java.endorsed.dirs} that is with
> java.endorsed.dirs=c:\java
> \jdk1.5.0_04\jre\lib\endorsed
>
> is sufficient?

You must follow the directions provided on the wiki.

https://authdev.it.ohio-state.edu/twiki/bin/view/Shibboleth/OSTwoUsrManJavaInstall

Which method you use to do the endorsement, putting the files in the 
standard location or providing an alternate location via the JVM 
property, is up to you.  Each method has its pros and cons.  Personally, 
given how broken the Sun provided code is I endorse these jars for the 
whole system and I've yet to encounter a problem (though I hear that 
most commercial app servers choke when you do this).


> The error is:
> 2006-07-30 22:07:07,078 ERROR [Configuration#validateConfiguration:574] 
> Configur
> ation file does not validate against schema
> org.xml.sax.SAXParseException: UndeclaredPrefix: Cannot resolve 
> 'test:SimpleElem
> ent' as a QName: the prefix 'test' is not declared.
>         at 
> com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXParseExc
> eption(Util.java:109)
>         at 
> com.sun.org.apache.xerces.internal.jaxp.validation.ErrorHandlerAdapto
> r.error(ErrorHandlerAdaptor.java:104)
>         at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError (
> XMLErrorReporter.java:382)
>         at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> XMLErrorReporter.java:316)
>
>
> I can see that the internal sun xerces parser is kicking in.
>
> Can the instructions at:
> https://authdev.it.ohio-state.edu/twiki/bin/view/Shibboleth/OSTwoDevManJavaBuild 
> <https://authdev.it.ohio-state.edu/twiki/bin/view/Shibboleth/OSTwoDevManJavaBuild>
> be updated such that I can clean build OpenSaml2.

The code is not going to build cleanly for at least a few more weeks as 
nearly all of the encryption and signature stuff is currently being 
rewritten and large chunks of binding support is being added.
--
Chad La Joie             2052-C Harris Bldg
OIS-Middleware           202.687.0124