I must of missed Vincenzo's post. I hadn't figured out why I had different behaviours on machines till I read your post and now you've explained it. Regarding deploying mailets, on some machines (1.4.2) only SAR style deployment worked for me while on others (< 1.4.2) jars loose in the lib directly worked.
This is a big "gotcha" for users. Lindsay -----Original Message----- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: 02 August 2003 21:57 To: James Developers List Subject: RE: JDK 1.4.2 and class loading Danny, > > jar:file:path/jarfile.jar!/ > That has always been the style of URL for jars as used to find files in > jars, but I'm surprised to see that jars now have to be specified this way. Same here. The javadocs haven't changed, and still say that "Any URL that ends with a '/' is assumed to refer to a directory. Otherwise, the URL is assumed to refer to a JAR file which will be opened as needed." Vincenzo upgraded to JDK 1.4.2, and found the file: protocol to no longer be working for JAR files. I did some quick searching on the web, and posted the results. The only way to get it working in JDK 1.4.2 was to provide an explicit jar protocol URL. As I said, I don't know if this is an intentional change in behavior, or a bug. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
