OpenSAML user discussion

[Chad La Joie <>]

Well, not to go against what Scott said there may be a way that you 
could do this.  The key is that a working JAXP parser must be in place 
prior to invoking the OpenSAML code.  I *believe* it would be possible 
to use java.lang.System#setProperties to set which JAXP parser is used. 
 I don't know that attribute names; you can find them in either the 
JAXP spec or in the Xerces and Xalan jar in the META-INF directory.  The 
later gives you both the attribute and it's value for using Xerces and 
Xalan.

So, whats the drawback and why don't we do this.  First, and it's really 
not a huge issue because it won't change, ever.  If there existed 
another JAXP parser that actually worked AND you wanted to use it, you 
wouldn't be able to if we did this in the code.  The larger issue, 
however, is that we're trying to support OpenSAML 2 on JDK 1.4.  JDK 1.4 
shipped with JAXP 1.1.  Endorsement allows you to replace/upgrade *some* 
of these additions to the JDK, JAXP being one of them.  You can not do 
this with the setting of System properties.

So, *if* you're using JDK 1.5, the properties solution *may* work for 
you if you do it before invoking OpenSAML.


Manuela Stanica wrote:
> Hello,
>
> Some people from our project (GÉANT2), who need to use an API we 
> developed based on opensaml, have come across a problem concerning 
> endorsed libraries. Endorsing Xerces and Xalan seems to be required in 
> order for the opensaml code to work, but this (using endorsed libs) is 
> not possible to do it Java Web Start setup which they are using. Xalan 
> and Xerces jars are configured in JNLP, however this does not make the 
> system load them instead of the default sun jars.
> Are there any possible workarounds?
>
> Thanks in advance,
> Manuela

--
SWITCH
Serving Swiss Universities
--------------------------
Chad La Joie, Software Engineer, Security
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 15 75, fax +41 44 268 15 68
,
 http://www.switch.ch