> > But, the point of what I am trying to say (and I will try to > clarify it > further in the document) is that by using Struts and JSP there is *NO* > enforcement that requires you to not use scriptlets. > [snip] > Putting Struts on top of JSP doesn't fix the warts in JSP. It > simply hides > them until your developers find them. > Jon; if I read you correctly a JSP engine would be better for having its scriptlets capability disabled. Or less radically allow the it to be specified in the web.xml file that scriptlets are not allowed for a given web-app. I think I buy that. In retrospect I even wish I had been able to do that on a few JSP projects past. Joerg Beekmann [EMAIL PROTECTED]
- You make the decision Velocity/Turbine vs. Struts/JSP Niall Pemberton
- Re: You make the decision Velocity/Turbine vs. S... Jon Stevens
- Re: You make the decision Velocity/Turbine vs. S... Jon Stevens
- Re: You make the decision Velocity/Turbine v... Joerg Beekmann
- Re: You make the decision Velocity/Turbine vs. S... Jon Stevens
- RE: You make the decision Velocity/Turbine v... Niall Pemberton
- Re: You make the decision Velocity/Turbine vs. S... Martin Cooper
- Re: You make the decision Velocity/Turbine v... Incze Lajos
- Re: You make the decision Velocity/Turbi... Wong Kok Wai
- Re: You make the decision Velocity/T... Incze Lajos
- Taking the plunge Kurt Olsen
- Re: You make the decision Velocity/Turbine vs. S... james . webster
- Re: You make the decision Velocity/Turbine v... Ted Husted
- Re: You make the decision Velocity/Turbine v... Craig R. McClanahan

