Well, I did say YMMV...8-) My advice is based on our successful development practice, and our interpretation of the Sun recommendations for using the extensions facility.
We develop on one machine, and run our apps on another, production machine; we have developer versions of the production software on our development machines for testing. In this kind environment, I don't see any problem. Also, the compiler is using the .jar file to resolve references to the API classes; if you deploy your application on a server that is using another vendors product, as long as you don't commit the sin of using any vendor-specific extensions, you should not have a problem (I've done this inadvertantly, with no problem). Once again, YMMV! At 12:46 PM 12/9/01 -0600, Christopher K. St. John wrote: >Doug Turner wrote: > > > > What works for me is to stick the servlet.jar in the standard > > jre/lib/ext directory > > > > servlet.jar is specific to a servlet container. The one >for Tomcat is different from the one for JRun, etc. To >be safe, it's best not to put servlet.jar into lib/ext. > > >-- >Christopher St. John [EMAIL PROTECTED] >DistribuTopia http://www.distributopia.com > >___________________________________________________________________________ >To unsubscribe, send email to [EMAIL PROTECTED] and include in the body >of the message "signoff SERVLET-INTEREST". > >Archives: http://archives.java.sun.com/archives/servlet-interest.html >Resources: http://java.sun.com/products/servlet/external-resources.html >LISTSERV Help: http://www.lsoft.com/manuals/user/user.html ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
