Обсуждение: Ways of loading the JDBC Driver (was RE: )
I'm going to rewrite the README file shortly so I'll add this one in. So far, the various ways of loading the driver are: WAGS Method --------------------------------------------------- .XX. Adding the .jar file into CLASSPATH .AX. Using -Djdbc.driver parameter on command line .XXX Place a copy of the .jar file into the jre/lib/ext directory ...X Place .jar file into wrapper.classpath parameter in jserv.properties Xnnn Merging the .jar file contents with the applet's classes nnnn Extracting the .jar file contents and not using any .jar files at all Where: W Applets through a web browser/server A Applications only (not AppletViewer) G Applications (also Appletsthrough AppletViewer) S Servlets And: X Will work n Will work, but not advised . Will not work Have I missed any out? PS: I've ignored the Standard Extensions method from here... -- Peter Mount Enterprise Support Officer, Maidstone Borough Council Email: petermount@maidstone.gov.uk WWW: http://www.maidstone.gov.uk All views expressed within this email are not the views of Maidstone Borough Council -----Original Message----- From: George Koras [mailto:gkoras@cres.gr] Sent: Monday, November 06, 2000 10:40 AM To: pgsql-interfaces@postgresql.org Subject: Re: [INTERFACES] In the file called jserv.properties there is a wrapper.classpath variable. This is the classpath for servlets. At least this is what worked in my case (Redhat Linux Release 6, Apache 1.3, Apache JServ 1.1.2). Peter Mount wrote: > So far, everyone who's asked me about problems with loading the driver with > Servlets had this problem. Setting CLASSPATH doesn't work, but putting the > .jar into jre/lib/ext does. > > Personally I've not done anything with servlets, so it's basically knowing > what works for everyone who's asked. Perhaps apache does pass CLASSPATH, but > the others don't for some reason. > > Peter George Koras (gkoras@cres.gr)
Peter Mount <petermount@maidstone.gov.uk> writes: > I'm going to rewrite the README file shortly so I'll add this one in. > > So far, the various ways of loading the driver are: > > WAGS Method > --------------------------------------------------- > .XX. Adding the .jar file into CLASSPATH > .AX. Using -Djdbc.driver parameter on command line > .XXX Place a copy of the .jar file into the jre/lib/ext directory > ...X Place .jar file into wrapper.classpath parameter in jserv.properties > Xnnn Merging the .jar file contents with the applet's classes > nnnn Extracting the .jar file contents and not using any .jar files at > all > > Where: > W Applets through a web browser/server > A Applications only (not AppletViewer) > G Applications (also Applets through AppletViewer) > S Servlets > > > Have I missed any out? > Well, technically there is no difference between the servlet case and the application case. You can start up JServ with the -Djdbc.driver argument, allthough I wouldn't recommend it. Apache JServ is only one example of how configuration is done. The new servlet APIs have better deployment specification than what you find in 2.0 API that JServ implements. Regards, Gunnar
Ah, that is why I've not heared of that way before this morning. Also, I rarely use -Djdbc.driver any how. PS: I just remembered another one: Putting the .jar file name in the manifest of the application's .jar file. I know that one works for applications, but not sure of the others. Peter -- Peter Mount Enterprise Support Officer, Maidstone Borough Council Email: petermount@maidstone.gov.uk WWW: http://www.maidstone.gov.uk All views expressed within this email are not the views of Maidstone Borough Council -----Original Message----- From: Gunnar R|nning [mailto:gunnar@candleweb.no] Sent: Monday, November 06, 2000 2:56 PM To: Peter Mount Cc: 'George Koras'; pgsql-interfaces@postgresql.org Subject: Re: Ways of loading the JDBC Driver (was RE: [INTERFACES]) Peter Mount <petermount@maidstone.gov.uk> writes: > I'm going to rewrite the README file shortly so I'll add this one in. > > So far, the various ways of loading the driver are: > > WAGS Method > --------------------------------------------------- > .XX. Adding the .jar file into CLASSPATH > .AX. Using -Djdbc.driver parameter on command line > .XXX Place a copy of the .jar file into the jre/lib/ext directory > ...X Place .jar file into wrapper.classpath parameter in jserv.properties > Xnnn Merging the .jar file contents with the applet's classes > nnnn Extracting the .jar file contents and not using any .jar files at > all > > Where: > W Applets through a web browser/server > A Applications only (not AppletViewer) > G Applications (also Applets through AppletViewer) > S Servlets > > > Have I missed any out? > Well, technically there is no difference between the servlet case and the application case. You can start up JServ with the -Djdbc.driver argument, allthough I wouldn't recommend it. Apache JServ is only one example of how configuration is done. The new servlet APIs have better deployment specification than what you find in 2.0 API that JServ implements. Regards, Gunnar