|
No, but it's not considered good practice to make database connections (or anything else that needs a password) directly from JSP pages. Matt -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Shannon O'Donnell Sent: Friday, October 06, 2006 3:56 PM To: Web Enabling the AS400 / iSeries Subject: Re: [WEB400] JTOPEN and Tomcat Would I need to import it differently or reference it differently than I did here in my JSP if I put it in the /context/WEB-INF/lib directory? %@page import="com.ibm.as400.access.AS400JDBCDriver" DriverManager.registerDriver(new com.ibm.as400.access.AS400JDBCDriver()); -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Matt.Haas@xxxxxxxxxxx Sent: Friday, October 06, 2006 2:36 PM To: web400@xxxxxxxxxxxx Subject: Re: [WEB400] JTOPEN and Tomcat There are two ways to do this. You can either put the jar file in Tomcat's lib directory or you can put it in the WEB-INF/lib directory for your application. Matt -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Shannon O'Donnell Sent: Friday, October 06, 2006 3:37 PM To: Web Enabling the AS400 / iSeries Subject: [WEB400] JTOPEN and Tomcat I would like to use some of the AS/400 specific classes in JTOPEN (jt400.jar) in my java server pages. Where would I define the classpath to the jar file(s) on my iSeries so that Tomcat will be able to compile the jsp's and I can use them? For example, my JSP might look like this: %@page import="com.ibm.as400.access.AS400JDBCDriver" % DriverManager.registerDriver(new com.ibm.as400.access.AS400JDBCDriver()); Where would I define and/or point the classpath so tomcat can find the jar file the as400jdbcdriver lives in? Thanks, Shannon O'Donnell
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.