[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: JAXP in debian



Hello Xavier,

[sorry for the private mail... sometime I will learn it... ]

Saturday, August 16, 2003, 1:28:54 AM, you wrote:
> However, if,for example, I want to use a newer version of xalan or
> xerces (xml-apis.jar) instead of Crimson (well, any other parser 
> implementing JAXP), you will have to use the endorsement Mechanism.
> see:
> http://xml.apache.org/xalan-j/faq.html#faq-N100CB
> (and specifically the last point)

If we want that this happens automaticly (updating the JRE build-in
version, if a package, which provides the jars is installed), then
we either have
* something like update-java-endorsed-dir, which updates the endosed
  dir of every registered/known JDK1.4. I'm not sure, whether this
  is available in non sun JREs
* have the bin/java or every startscript, which requires one of this
  JCP APIs to set the -Xbootclasspath accordingly. For this I could
  add somthing to my proposed 'getjavaclasspath' mechanism.

For 1.3 it seems that this must be even more radical (i.e. use of
diversion or simple rm the offending jars), as both mechnism aren't
included in that release...

For the xml packages, it might also be interesting to set the
default parser (or other properties), if more than one are in the
classpath. This could also be added to 'getjavaclasspath'

<sidenote>I get more and more the feeling, that java isn't really
fit for being packaged. More or less everything is settled around
changing APIs, one big piece, where you can't update just one single
jar and so on and a really unfriendly license...</>

> Apparently, having the jar files in /usr/share/java  will become useless 
> or am i wrong?

Even if we find a way to do it differently, it is a good place to
have all jars. On the other hand, if it happens, that we only
symlink there and anyway use a different path to finaly access the
jar, it might be obsolete...

> Isn't this a problem for the  xml related packages as 
> xerces,saxon,gnu-jaxp,xalan) ???

Yes. And it will probably become a problem for much more packages, as
there are other JCP packages, which became/become included in the
defualt JRE.

Jan



Reply to: