|
Hello, I'm new to websphere and I'm having considerable trouble getting websphere on the AS/400 to recognize classes in the classpath as opposed to classes in the servlets directory. I'm trying to move away from having support classes loaded dynamically like servlets. To do this instead of placing the classes in a directory specified in servlets.properties, I place them in the classpath specified in jvm.properties. I've read the websphere documentation for the AS/400 (what there is of it), redbooks, and IBM manuals. I tried every possible variation to try to get websphere to recognize the classes, but it just won't see them. It is very frustrating. Any help or suggestions that anyone could provide would be greatly appreciated. I include the following to help describe my situation: I'm running WebSphere 1.1 on an AS/400 under V4R3 If I place the classes in the servlets directory, the classes are found I was able to place the AS/400 toolbox file (jt400.jar) in the classpath and it is found I explicitly use CRTJVAPGM to make sure the Java transformer creates the necessary program objects I've tried placing the individual classes in the classpath and I've tried making them into a jar file. Neither variation works. I use HTTP command to check the servers classpath and it is set correctly. I can't understand how webshere can appear to find the toolbox classes (jt400.jar) in the server classpath, but it can't find my classes. I can't make sense of it. Anyone have any ideas? Thanks. Frank DeSarro +--- | 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/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.