×
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.
Putting things in the ..../ext directory will get rid of your CLASSPATH
problem but will most likely introduce new problems like slow startup times
once a large amount of jars have been added to the ext directory. When the
JVM starts, all of the jars in the ext directory will be looked at as I
understand it.
Here's some reading for you:
http://hubpages.com/hub/Java_Extension_Mechanism
Putting things in the ext folder is like changing the default jobd on the
iSeries - it effects everybody. Personally I think you should go with the
dataqueue approach and spawn a new thread for each request coming into the
data queue. This would solve all of your issues with classpath and
throughput, AND if I recall correctly there is an open source project that
does exactly this at
http://mowyourlawn.com/RPGChartEngine.html ;-)
Aaron Bartell
http://mowyourlawn.com
On Thu, Jun 12, 2008 at 7:15 AM, Bradley V. Stone <bvstone@xxxxxxxxxxxx>
wrote:
I'm wondering if this wouldn't have the same issues that CLASSPATH would.
If another application has already been run and uses the JAVA_HOME env.
variable, you can't keep movng your JARs around.
Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com
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.
midrange.com
