[EMAIL PROTECTED] wrote: > Hi Gopal, > > Thanks for the suggestions; they both do indeed work. > > But this still doesn't seem to be a very good situation: To compile a > modern version of Xalan, I first need a compiled version of modern Xalan. > i.e., as soon as I make a change which would be incompatible with the > current Xalan jar I'm using on the bootclasspath or as the target of the > java.endorsed.dirs property, I've got to use an older JDK to build a new > jar. Then I can return to 1.4.x and use this new jar for additional > compilations/tests. > > Because of the way Sun JDK's are packaged--with everything including Xalan > and the kitchen sink in rt.jar--I've come to the conclusion that no good > solution exists on this platform. In JDK's that are packaged with > different components in different jars, it'll be possible to exclude the > appropriate jars from javac's bootclasspath so that it will be possible to > dynamically build entirely new Xerces/Xalan jars without reference to > pre-existing ones. It's just unfortunate that Sun JDK's aren't packaged > differently. > > Can anyone else see any workaround? Anybody know whether this is how Sun > JDK's will always be packaged?
After reading this thread in xalan-dev, I think I understand the issue. I would suggest as a workaround to use the -bootclasspath option of javac and prepend the *new* xalan classes before rt.jar. As for a future fix, I believe Sun has current plans to rename all org.apache.** classes to some other package in the JDK 1.4.2 time-frame. This should also allow apache developers to use apache packages independent from the core JDK classes. However, the package renaming is *not* completely straight forward as there may be code changes that need to be made, particularly in the Xalan codebase if I recall. -Edwin > > Cheers, > Neil > Neil Graham > XML Parser Development > IBM Toronto Lab > Phone: 905-413-3519, T/L 969-3519 > E-mail: [EMAIL PROTECTED] > > > > > |---------+----------------------------> > | | Gopal Sharma | > | | <Gopal.Sharma@Sun| > | | .COM> | > | | | > | | 09/26/2002 10:55 | > | | AM | > | | Please respond to| > | | Gopal Sharma | > | | | > |---------+----------------------------> > >>---------------------------------------------------------------------------------------------------------------------------------------------| > | > | > | To: [EMAIL PROTECTED], Neil Graham/Toronto/IBM@IBMCA > | > | cc: [EMAIL PROTECTED] > | > | Subject: Re: can Xalan be compiled under JDK 1.4.x? > | > | > | > | > | > >>---------------------------------------------------------------------------------------------------------------------------------------------| > > > > Gopal Sharma wrote:- > | The solution, I found is -- change the sequence of class loading using > | bootclasspath means use: > | > | % javac -bootclasspath > | $L_HOME/xalan.jar:$L_HOME/xsltc.jar:$JAVA_HOME/jre/lib/rt.jar > | -J-showversion -verbose > src/org/apache/xalan/templates/FuncKey.java > | > | It works in both Sun Jdk 1.4 and 1.4.1. > > I don't know why it didn't work earlier for me. But anyway, It works: > > Drop new xalan.jar/xsltc.jar in jre/lib/endorsed and simply use > followiing: > > % javac -J-showversion -verbose > src/org/apache/xalan/templates/FuncKey.java > > It will work great. > > Thanks > - Gopal > > >
