Re: [Openjnlp-devel] Lazy jars

[Kevin H. <ke...@na...>]

On Wednesday, May 8, 2002, at 02:34 , Mario Cormier wrote:

> I tried running a JNLP app that used lazy loading of some jars, and it=20=

> simply didn't work because of ClassNotFoundExceptions.=A0 Going =
through=20
> the code, I noticed that nothing is done about lazy jars.=A0 My=20
> understanding of the spec. is that these jars should always be loaded=20=

> over the network, like applet jars.=A0 Is so, the correct way to=20
> implement it would be to add the remote (http:) URLs

You are correct, OpenJNLP does not yet support lazy jars. Unfortunately,=20=

your interpretation of loading lazy jars doesn't seem to agree with the=20=

specification. Lazy jars still are cached locally, but are not retrieved=20=

until needed. The pertinent part of the JNLP specification is Section=20
4.4, "Parts and Lazy Downloads". For this reason I don't think I can use=20=

your suggested changes (as good as they are) but I will use your work as=20=

motivation to get lazy jars implemented.

[...]
> Also note that on the Windows 2000 system I'm using to test this, the=20=

> FileCache.toSafeURL() method breaks the local file: URLs, even though=20=

> it seems like the correct thing to do.

Yeah, what I've discovered is that the "file" URL protocol handler from=20=

Sun is completely broken. You can't use correct URL encoding as per RFC=20=

2396 for file paths. I had to back out the FileCache.toSafeURL() calls.=20=

I ran into some serious problems with that and the way RMI works.=20
Something has to be done about spaces in names in the cache. Blah.