- From: Michael S. Zick <mszick@pflash.com>
- Date: Wed, 10 Nov 1999 06:02:33 -0600
- To: www-jigsaw@w3.org
A note on the following problem -- I have read of problems with some OS/VM implementations based on a difference on how relatives paths are resolved -- It seems that the JAVA classloader and the system's dynamic library loader (the VM native code lives in a dynamic library) differ in their handling of relative paths. Without knowing your OS/JAVA combination or the full details of the above problem -- Absolute paths are good -- Perhaps not required but don't be surprised if changing to absolute paths fixes a problem. Mike. On Tue, 09 Nov 1999, Fetty Gerhard wrote: > Maybe this saves time to any other newbies ... > ... or someone might fix it ... > > Running JigSaw 2.0.3 on NT. > The jigsaw.bat file that is intended to start the server issues the > command > > java -classpath ..\classes\jigsaw.zip; org.w3c.jigsaw.Main -root > ..\Jigsaw > > When surfing around the local web-pages (somewhere under WWW), clicking > on any link produces the following message: > > org.w3c.tools.resources.IllegalAttributeAccess: Illegal attribute value > null for frames > void org.w3c.util.CachedThread.run() > > The followed web-page takes minutes to load. > > Took me hours to realise that if you start Jigsaw with an absolute path, > everything works like a charm: > > java -classpath ..\classes\jigsaw.zip; org.w3c.jigsaw.Main -root > c:\home\Java\Jigsaw\Jigsaw > > > > Gerhard Fetty
Received on Wednesday, 10 November 1999 07:13:03 UTC