Darren,
Thanks for the "classpath is fixed" hint - sounds awfully final!

Our current project fits the batch profile where we have a "never ending"
job monitor for the next workbook to process.

And, as I have mentioned, I prefer using default/traditional landscapes
with the intention to make the project easy to understand/maintain.

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of darren@xxxxxxxxx
Sent: Thursday, May 30, 2013 7:14 AM
To: Java Programming on and around the IBM i
Subject: RE: .jar/.tar file question #2

There are some downsides to the classpath argument. Once you run any java program in your job, the classpath is fixed at its current value. For example, if your job calls some java program, other than POI, and then you try to run your POI using program with the additional classpath requirements, it will fail. What this all really means is that if you're going to run java in a persistent job, like an interactive session, then the ProdData/java directory has some advantages because its in the default classpath.

To avoid all of this confusion, its best to try and run the java using program in a batch job where the JVM is started and ended in predictable ways.




From: Dan Kimmel <dkimmel@xxxxxxxxxxxxxxx>
To: Java Programming on and around the IBM i
<java400-l@xxxxxxxxxxxx>,
Date: 05/29/2013 05:24 PM
Subject: RE: .jar/.tar file question #2
Sent by: java400-l-bounces@xxxxxxxxxxxx



You really don't want those in Java400/ext. That's where java extensions go. Java extensions are not subject to the same kind of security checks as normal jars and it is really hard to override jars in that path. For the most part, only security extensions to java should go in the ext path.

Create a directory in the IFS and put all your POI jars in there. When you start your RPG program, make sure the classpath includes a full path to
*EACH* jar.

FWIW, depending on what operating system you're using, java will reside in either /QIBM/ProdData/Java400 or /QOpenSys/QIBM/ProdData/Java. All the J9 JVM's live only in QOpenSys.

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx
] On Behalf Of Gary Thompson
Sent: Wednesday, May 29, 2013 3:32 PM
To: Java Programming on and around the IBM i
Subject: .jar/.tar file question #2

I think I now have the .jar files I need (thanks Gary and Darren) and I think these need to be copied to: /QIBM/UserData/Java400/ext

But only have /QIBM/UserData/ but no Java400/ext

Do I just create these directories/folders ?
--
This is the Java Programming on and around the IBM i (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 is the Java Programming on and around the IBM i (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 is the Java Programming on and around the IBM i (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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.