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





Hello,

I'm creating a database frontend using JSP pages on WebSphere 2.0.2, and I'm
currently running into a stupid problem. One of my JSP pages imports a class
(which is located in the JSP page document-root). Up to this point everything
works
as expected. But now this class needs to import classes from a JAR file. The big
question I have is how do I tell WebSphere (specifically the pageCompile
servlet)
what ClassPath to use? I've tried pretty much every option in the WebSphere
administration interface - none of them seems to have any effect on this
problem.
I also tried putting the JAR file into <installation-root>/lib, where it should
be
picked up automatically, but it isn't.

Can anyone enlighten me on this?

TIA

Christian Glodt





Electronic information is not secure, therefore the Entreprise des Postes et
Telecommunications accepts no responsibility whatsoever for the contents of this
 message, which is intended for the addressee only. Its contents and any
attached files are strictly confidential. If you have received this message in
error, please telephone the following number 4765-1.


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.