Re: TypeBrowser -- jawin newbie

Hi Patrick and Josh (good to hear from you, are you still "swamped" by
work?)

Josh Passenger wrote:

>
> Perhaps you ened to bootstrap the deployed Xalan, Xerces and XML-APIs jars
> onto your classpath if they are available from your JVM?

I just checked the Classpath setting from the manifest file:

Class-Path: ../lib/jawin.jar lib/xalan.jar lib/xercesImpl.jar
lib/xml-apis.jar

So, if the JVM does not contain Xalan, Xerces, etc, they should be
loaded from the lib-folder (if the JVM contains these itself (eg.
JDK1.4), they will be loaded before these on the classpath). That is, if
one launches the typebrowser from the typebrowser folder with:
        java -jar jawinBrowser.jar

And according to Patricks cmd-prompt, that is what he did.

But you're right, Josh, that there could be other mysterious classpath
problems (or Java version problems, that we haven't meet before). The
immediate places Patrick should look for problems are (besides the ones
Josh already have suggested):

- is the %CLASSPATH% environment variable set? From a command prompt:
"echo %CLASSPATH%". (I am not sure, whether the Classpath-setting in a
manifest actually "adds" to this, or "replaces" it for the current JVM
instance, I will have to look that up).

- is there anything in the ext-dir for Java (JRE-path/lib/ext - example:
C:\jdk1.3.1_02\jre\lib\ext).

- the new >JDK1.4 "endorsed" dir, does that exist and contain anything
(JRE-path/lib/endorsed).

Finally you can try the "-verbose:class" option like:
        java -verbose:class -jar jawinBrowser.jar
(probably a good idea to pipe it to a file, as it gives LOTS of output),
this will show from which jar's each class gets loaded. You should
probably look for classes in the the javax.xml, the org.xml and
org.apache.xalan packages - do they get loaded from unexpected jars?

>
> I think the package structire of the browser might have been rearranged
> recently, please make sure that out Xalan Xerces xml-apis are on your
> classpath, I think the maifest.mf in jawinBrowser.jar points to
> ../libxalan.jar which is probably incorrect.

I just checked that as cited above, and as far as I can tell it should
be correct (both in the CVS head and in the last binary release).

>
> Guys, perhaps we need to distribute a batch file like we did some time ago
> that sets of the classpath etc?

Yes, if this comes out to be a classpath problem, that we could have
avoided with a well written batch file (and it is unavoidable with the
Classpath setting in the manifest of the jar), I think we should
definitely look into that.

Another thing we could do is to write as much debug info as we can get
about Java-version, Xalan, Xerces, classpath's, etc. on typebrowser
startup (I think I have some old code showing how to use the
java.lang.Package to retrieve the version information from a manifest
file in a jar, I could try to dig that out).

Best Regards
Morten