Re: Reducing the size of JT400 / JTOpen JAR?

["colin williams" <colin.williams@xxxxxxxxxxxx>]

David,

one option might be to start the JVM in verbose mode so that you can see
exactly what classes are getting loaded from JT400, then repackage those in
your own jar file.

cheers
Colin.W


----- Original Message ----- 
From: "David Gibbs" <david@xxxxxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Tuesday, August 31, 2004 7:00 PM
Subject: Reducing the size of JT400 / JTOpen JAR?


> Does anyone have some pointers are a good way to reduce the size of the
> JT400 / JTOpen JAR file?
>
> I've already removed the com.ibm.as400.vaccess, com.ibm.as400.util, and
> com.ibm.as400.micro packages, as well as all the GIF files (my
> application runs on green screen).
>
> Thanks!
>
> david
>
> --
> This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
>
>


This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.