You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Berin Lautenbach <be...@wingsofhermes.org> on 2004/02/15 12:22:18 UTC

JRE 1.4 endorsed mechanism

Hello all,

I'm trying to get xml-security working again in gump (it's been out for 
quite a while).

I'm quite sure I've just hit a common problem, but I have no idea how to 
easily overcome it.

The xml-security library requires that xalan be installed in 
JDK_HOME/jre/lib/endorsed to override the old version that comes with 
JDK 1.4.

Looking at the output from the last gump run for security, it would 
appear that the old library that comes with 1.4 is being used :

http://gump.covalent.net/log/xml-security.html

Is there a "standard" way to overcome this in Gump?  (E.g. - get Gump to 
copy newly build xalan.jar to the endorsed directory.)

Cheers,
	Berin



Re: JRE 1.4 endorsed mechanism

Posted by Berin Lautenbach <be...@wingsofhermes.org>.
Stefan,

With thanks!  I hoped there would be a more elegant solution than just 
copying the file to the endorsed directory :>.

Cheers,
	Berin

Stefan Bodewig wrote:

> On Sun, 15 Feb 2004, Berin Lautenbach <be...@wingsofhermes.org> wrote:
> 
> 
>>The xml-security library requires that xalan be installed in
>>JDK_HOME/jre/lib/endorsed to override the old version that comes
>>with JDK 1.4.
> 
> 
> With Xerces-J we are going even further, we put the CVS HEAD jar onto
> the bootclasspath so it gets used instead of Crimson.  This should be
> possible with Xalan as well, and to me it even looks as if we'd use
> the same mechanism (type="boot" on the <jar> element).
> 
> 
>>Looking at the output from the last gump run for security, it would
>>appear that the old library that comes with 1.4 is being used :
> 
> 
> Seems build.clonevm is becoming a FAQ 8-)
> 
> The bootclasspath trick is not working since xml-security's <junit>
> task runs in a different Java VM by using fork="true".  Ant's CVS HEAD
> uses a new Java system property to ensure that the forked VM uses the
> same bootclasspath as the one running Ant.
> 
> I'll enable that property for xml-security in a few minutes.
> 
> Cheers
> 
>         Stefan


Re: JRE 1.4 endorsed mechanism

Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 15 Feb 2004, Berin Lautenbach <be...@wingsofhermes.org> wrote:

> The xml-security library requires that xalan be installed in
> JDK_HOME/jre/lib/endorsed to override the old version that comes
> with JDK 1.4.

With Xerces-J we are going even further, we put the CVS HEAD jar onto
the bootclasspath so it gets used instead of Crimson.  This should be
possible with Xalan as well, and to me it even looks as if we'd use
the same mechanism (type="boot" on the <jar> element).

> Looking at the output from the last gump run for security, it would
> appear that the old library that comes with 1.4 is being used :

Seems build.clonevm is becoming a FAQ 8-)

The bootclasspath trick is not working since xml-security's <junit>
task runs in a different Java VM by using fork="true".  Ant's CVS HEAD
uses a new Java system property to ensure that the forked VM uses the
same bootclasspath as the one running Ant.

I'll enable that property for xml-security in a few minutes.

Cheers

        Stefan
-- 
http://stefanbodewig.blogger.de/