Well, I finally got it working! Here's a brief rundown of what I did (Most of which I got from you guys) because it might be helpful to the next newbie to Torque...
1) JBuilder 5 will NOT work for Torque in it's web environment. The ClassLoader in JBuilder is bunk. I ended up downloading NetBeans 3.4 to run in a web environment. Jbuilder will run main() classes fine however. I've got an extra machine that I might install the latest JBuilder release on to test it and see if the same bug exists. 2) Grabbed the new Torque 3.0 RC1 instead of the beta 4 release. 3) Used the org.apache.torque.dsfactory.TorqueDataSourceFactory instead of the Jdbc2Pool. If there's any gain in the Jdbc2Pool, I'll switch back. I just got it working, so I haven't tested it with the pool yet. 4) Put the torque.properties file in a path outside of my web-app, and pass my InitServlet the absolute path to that file. This took the guesswork out of trying to figure out where that file should go. Like was said earlier, it will either work or it won't, but you'll know it's not where the file should go that's breaking. 5) Put everything in the torque/lib folder into WEB-INF/lib. The one caveat to this is that Tomcat 4.0.x has an XML bug and the solution is to upgrade to 4.1.x. The easier way around this is to include the full xerxes.jar under WEB-INF/lib also. This took care of all the XML errors I got with Torque. I did not include any build-time stuff at all. 6) Crossed my fingers when I started my Tomcat instance after getting my InitServlet configured. :-) Thanks again for all the help guys. It is appreciated. Beer... Bob __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ -- To unsubscribe, e-mail: <mailto:turbine-torque-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-torque-user-help@;jakarta.apache.org>
