I've just been playing around with the web app compilation for Tomcat and was just curious as to its benefits? Since the jsp's are now compiled and the mappings from the generated-web.xml are added to the web.xml you don't need the jsp's do you? This will make the initial requests faster I would imagine as the .jsp's are now compiled. Is that accurate? Are others using this approach for deployment?
Steve -----Original Message----- From: James Childers [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 11:18 AM To: Struts Users Mailing List Subject: RE: Are .jsp files required ? > Hi ! > Are .jsp files physically required on a production server ? If you are wanting to use JSPs, then yes. > I would prevent any change by my customer and think that > "reloading=false" is not safe enougth. Prevent any changes by the customer to what? The JSPs? The customer can't change the JSP, unless they have access to your directory. (Which they won't, unless you have been very silly.) If you're really concerned about this most modern servlet containers allow you to put your JSPs under WEB-INF; the container is the only thing that has access to that. > I think that .class should be enougth but delete a .jsp file > generates an exception (even with reloading=false in web.xml).. > I want produce .java and .class with ant tasks (<jspc> and <javac>). This is done by the container. Look under your WEB-INF directory somewhere and you will find .java/.class files that have been generated. -= J --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
