Yes, that sounds right to me. Even QGPL is, to me, off-limits.
/QOpenSys is just too >strange< for me (See Joe Hertvik's Admin Alert article)


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

The only best practice I'm aware of is not using IBM Q* folders for your own stuff :)

/QOpenSys is an exception as it is the root of a file system.

But I wouldn't store anything in .../QIBM/...

/JavaTools/POI seems reasonable to me...

Charles


On Thu, May 30, 2013 at 9:10 AM, Gary Thompson <gthompson@xxxxxxxxxxx>wrote:

Charles,
I thought of that, and wondered about "best practices" or "traditions"
for storing additional java resources.

Will others find my changes easy to understand and follow ?

Maybe put POI and such under /JavaTools/ ?

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

There's really no need to use /QOpenSYs/QIBM/...

You could simply create a folder off the root, /POI

Charles


On Wed, May 29, 2013 at 7:04 PM, Gary Thompson <gthompson@xxxxxxxxxxx
wrote:

Dan,
I can barely spell Java, so I really appreciate the advice, and,
unfortunately, don't grasp the meaning of your FWIW comments, but am
keeping your post with the thought that the meaning will emerge in
time.

This is the path where I *think* I want to create the directory you
suggest:

/QOpenSys/QIBM/UserData

So, if the new directory is POI, then:

/QOpenSys/QIBM/UserData/POI

And class path:

/QOpenSys/QIBM/UserData/POI/poi-thing-1.jar
/QOpenSys/QIBM/UserData/POI/poi-thing-2.jar
. . .
/QOpenSys/QIBM/UserData/POI/poi-thing-6.jar

Hmm, my class path example looks ridiculous.


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

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.


--
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-2022 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.