RE: (no subject)

        Yeah... it doesn't mention Xalan on that page, but I searched
the forums on java.sun.com and there were a couple people with the same
problem and thats what they had to do, that and the Xalan packages are
in rt.jar. I don't know how it handles that, but I am under the
impression you can override just about anything.
        As a matter of fact, I have log4j-1.2.8 in my endorsed
directory, but log4j-1.2.7 is in a different directory and included in
the *SYS level CLASSPATH on my iSeries. When I run my program, which
sets the java.endorsed.dirs switch in the QIBM_RPG_JAVA_PROPERTIES
variable and then calls my Java method, it loads my newer version of
log4j from my endorsed dir rather than the older version in the
CLASSPATH. So, apparently (read: assumption being made) you can use it
to override anything in your classpath to a newer version. I can think
of a few times in the past where knowing this could have been extremely
handy.

-Dan Feather

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Clapham, Paul
Sent: Thursday, July 07, 2005 4:44 PM
To: Java Programming on and around the iSeries / AS400
Subject: RE: (no subject)

Hmmm. I already looked at that and, since Xalan wasn't in the list of
things that were allowed to be overridden, I assumed that it wouldn't
work for you. But if it does, who can complain? The boot classpath is
somewhat of an ugly hack anyway. 

PC2

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Feather
Sent: July 7, 2005 14:37
To: Java Programming on and around the iSeries / AS400
Subject: RE: (no subject)

Thanks for the response. I actually came up with a solution and
explanation already and hadn't posted it to the list yet.

Apparently, from what I have read, this is an issue with Java version
1.4.x. They included xalan version 2.4.something in rt.jar, along with
some other apis. You can override the versions included by passing
-Djava.endorsed.dirs=/some/path/to/your/jars to the JVM when you call
it. It is the "Endorsed Standards Override Mechanism."
http://java.sun.com/j2se/1.4.2/docs/guide/standards/index.html

I had did not run into this problem running my code with Java 1.5 on my
PC, so from what I can see they may have rid java of this "issue" with
1.5.

I am calling my Java from RPG so I set the QIBM_RPG_JAVA_PROPERTIES
environment variable in my job to include the above switch before I
called my code and it worked like a charm. It also turns out, that the
problem I was having last week with the "No suitable driver found" issue
(a different thread) may have been solved by getting it to load the
correct version of xalan as well... but I had already coded around that
problem so I am not certain.

-Dan Feather