× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Scott

What is your reasoning behind not wanting to put code into ext? Is it primarily to prevent the issue of duplicate classes, and the incorrect class being loaded?

Are there any instances where you would recommend or use ext? For example, I prefer to put other databases' JDBC drivers there.

Thanks
Craig Pelkie


----- Original Message ----- From: "Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, March 22, 2010 12:43 PM
Subject: Re: Scott's Excel stuff and Giovanni's XLPARSE2


Okay, so I did say it more recently than 2004...

But if it helps, I really really really regret saying that! :)

When I speak about this stuff, I tell people not to use the "ext"
directory, and my recent articles (like the following one) explain how
to set up an IFS directory structure and put it in your CLASSPATH.

http://systeminetwork.com/article/new-poi-release-brings-excels-xlsx-support-rpg

Unfortunately, when I say something st00pid and it gets published, it's
hard to take it back :)


On 3/22/2010 1:03 PM, Dennis Lovelady wrote:
I don't suppose it could have been from this July, 2007 article? "POI
Updated to Version 3.0.1"
http://systeminetwork.com/article/poi-updated-version-301/

Quoting: "Personally, I prefer to put the POI JAR files in the Java
"extensions" (/qibm/userdata/java400/ext) IFS directory. Once that's done,
they're installed and there's no need for me to monkey with my CLASSPATH,
because any JAR file in the extensions directory will automatically be found
and used by the JVM. Basically, any JAR file in that directory is considered
a "public tool" available to any Java software on the system."
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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.