Réf. : RE: init problem with jdk1.4.2_05

[va...@bull.net]

Thanks for this quick response !
Please can you send me the jar ?

Valerie





"Perry Dillard" <pe...@epok.net> sur 13/10/2004 19:22:42

Veuillez répondre à security-dev@xml.apache.org

Pour : <se...@xml.apache.org>
cc :
Objet :     RE: init problem with jdk1.4.2_05


You need to get the latest code from CVS and build it, or I can send you a
patched xmlsec-1.1.jar file that circumvents this problem. Luckily this
change was very isolated and it was easy to patch the one place where this
problem occurs.

=Perry

________________________________________________________________________
This message and any attachments are confidential and may be privileged or
otherwise protected from disclosure. If you are not the intended recipient,
please telephone or email the sender and delete this message and any
attachment from your system. If you are not the intended recipient you must
not copy this message or attachment or disclose the contents to any other
person. For further information about Epok Inc please see our website at <a
href="http://www.epok.net">http://www.epok.net</a> or refer to the Epok Inc
office.

-----Original Message-----
From: valerie.bauche@bull.net [mailto:valerie.bauche@bull.net]
Sent: Wednesday, October 13, 2004 10:17 AM
To: security-dev@xml.apache.org
Subject: init problem with jdk1.4.2_05

I saw this problem in a previous post but it did not give a correct
solution. So I ask it again :
under jdk1.4.2_05, the command org.apache.xml.security.Init.init()
throws the following error :
java.lang.IllegalAccessError: tried to access field
org.apache.xpath.compiler.FunctionTable.m_functions from class
org.apache.xml.security.Init

Does somebody have the solution for that ?

RE: Réf. : RE: init problem with jdk1.4.2_05

[Perry Dillard <pe...@epok.net>]

Well I'd have to wholeheartedly agree with that. I don't really understand
why Sun did that instead of just letting us put what we want to come first,
first in the CLASSPATH. Luckily there was a very specific change, in fact it
was completely isolated, so you can get the right stuff out of CVS very
easily. That's what I did and just patched the one or two source files that
were affected.

Hopefully we'll be getting a 1.2 version soon so this will be a non-issue.

=Perry
 
________________________________________________________________________
This message and any attachments are confidential and may be privileged or
otherwise protected from disclosure. If you are not the intended recipient,
please telephone or email the sender and delete this message and any
attachment from your system. If you are not the intended recipient you must
not copy this message or attachment or disclose the contents to any other
person. For further information about Epok Inc please see our website at <a
href="http://www.epok.net">http://www.epok.net</a> or refer to the Epok Inc
office.

-----Original Message-----
From: Scott Cantor [mailto:cantor.2@osu.edu] 
Sent: Wednesday, October 13, 2004 10:41 AM
To: security-dev@xml.apache.org
Subject: RE: Réf. : RE: init problem with jdk1.4.2_05

> Unfortunately this is a hack workaround since the xalan xslt apis are not
> part of the actual endorsed override apis.

Of course, but the hack is that Sun put these classes into the JDK in the
first place. One leads to another. Using a CVS build of a package is far
worse in many environments.

-- Scott

RE: Réf. : RE: init problem with jdk1.4.2_05

[Scott Cantor <ca...@osu.edu>]

> Unfortunately this is a hack workaround since the xalan xslt apis are not
> part of the actual endorsed override apis.

Of course, but the hack is that Sun put these classes into the JDK in the
first place. One leads to another. Using a CVS build of a package is far
worse in many environments.

-- Scott

RE: Réf. : RE: init problem with jdk1.4.2_05

[Perry Dillard <pe...@epok.net>]

Unfortunately this is a hack workaround since the xalan xslt apis are not
part of the actual endorsed override apis. The only reason it works to do
that is because they get loaded in the same classloader as the xerces. You
might as well just put all your jar files in one directory and specify that
directory to -Djava.endorsed.dirs.


=Perry
 
________________________________________________________________________
This message and any attachments are confidential and may be privileged or
otherwise protected from disclosure. If you are not the intended recipient,
please telephone or email the sender and delete this message and any
attachment from your system. If you are not the intended recipient you must
not copy this message or attachment or disclose the contents to any other
person. For further information about Epok Inc please see our website at <a
href="http://www.epok.net">http://www.epok.net</a> or refer to the Epok Inc
office.

-----Original Message-----
From: Scott Cantor [mailto:cantor.2@osu.edu] 
Sent: Wednesday, October 13, 2004 10:33 AM
To: security-dev@xml.apache.org
Subject: RE: Réf. : RE: init problem with jdk1.4.2_05

> Thanks for this quick response !
> Please can you send me the jar ?

Note the other work-around is just to endorse xalan to override the broken
JDK classes.

-- Scott

RE: Réf. : RE: init problem with jdk1.4.2_05

[Scott Cantor <ca...@osu.edu>]

> Thanks for this quick response !
> Please can you send me the jar ?

Note the other work-around is just to endorse xalan to override the broken
JDK classes.

-- Scott