Re: [Jython-users] "bad" jars

[D-Man <ds...@ri...>]

On Fri, Apr 13, 2001 at 10:06:57PM +0000, Finn Bock wrote:
| [D-Man]
| 
| Just to clear up possible confusion: Jython doesn't load anything from
| jars on CLASSPATH. Instead it uses the java mechanism for loading
| classes and resources from such jars. Jython only scans the jars to
| detect java packages (and support import *).

Ok.  I was refering to the "sys-package-manager" messages that appear
on startup.

| If you don't need this scanning, you can manually tell jython which java
| packages you have:
| 
|   sys.add_package("my.javapackage.core")
|   sys.add_package("my.javapackage.util")

I assume this will work after the sys-package-manager says "ignoring
corrupt jar file"?  Before I was getting "No module 'my' found" (using
your package name above).

| >Is there a way to turn off jython's processing and caching of the
| >jar's information so I can use this modified (err, hacked <wink>) jar?
| >If not, I can write some Java code to run through some tests.
| 
| Have you checked if the JVM will load classes from such a corrupt jar? I
| wouldn't be too surprised if some JVMs will ignore a corrupt jar.

I suppose some might.  I've been using it with JDK 1.1.8 on a Windows
box.  I also tested it a while ago on a Solaris 8 system.  I haven't
heard any complaints yet about it totally hosing the system with other
VMs.  Officially we only support JDK 1.1.8 because a third-party
library we use only officially supports JDK 1.1.8.  We do know that
the product works with JDK 1.2.2 because several customers have
reported using it.

| I can't think of a way to achieve your goal without resorting to a file.

Ok, thanks for the help.
-D