Howdy, >Long run? I've been watching TC a long enough and have changed >a number of times the scheme of including the CLASSPTH. In the >long run, are you absolutely sure what is going right now will be >stay same ... say in next 5 years?
I'm sure tomcat will implement the servlet specification standard, yes. I'm sure the servlet specification standard will not mention anything about $CLASSPATH in server-specific startup scripts, yes. /WEB-INF/lib is the standard way to go. It's the only way to go if you don't want to change scripts when changing servers. If you had put the libs there when using tomcat 3.x, you wouldn't have had to move them when moving to 4.x, etc. >What's the time frame for "the long run" mean? More than 5 years? Any time other than the initial beginner setup. You want to be able to setup from scratch automatically, e.g. using an ant script. You want a 3rd party person to be able to deploy your app. That's why the spec is there. That's why the idea of a .war file exists. Sure, you could write detailed instructions and require a specific version of tomcat with your modifications to tomcat's startup script, but good luck getting people to use (much less buy) your app then ;) Obviously it's your app, your company (or university or whatever), so it's your call. In my personal experience, every place I've worked and every boss I've had always insisted on portability and standards-compliance as much as reasonably possible. It's saved us many times. Now I insist on the same with all the developers that work for me, all the projects I'm responsible for, etc. And if I had a dollar for every time it's paid off, I'd be rich ;) Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
