Hi!
> >
> > So, JSP != "Java code in HTML". Can be, but don't have to be.
> >
> > /Rickard
>
>
> true, rickard, but then the control would haave to come from the app
> developers such that all real code is in the app layer and not in the jsp
> layer. The problem with jsps is that code *may* always leak in due to
poor
> design/lazy developers.
Add a test suite that searches for "<%" in the JSP's. If it finds one the
test fails :-)
If you simply say "Java code is banned in JSP" that should be enough. If
not, then fire the ones that break it. I mean, come on, how unreasonable is
it to use rules in developing an application?
> how about a servlet-template architecture (such as webmacro)? we used to
> develop our apps using jsps but I fast found that people were trying to do
> things 'quick and dirty' by sticking code into jsps. needless to say this
> pissed the hell outta me and now we use webmacro ... which, in my opinion,
> is a fast and flexible templating engine ...
So, what you have done is turn off the possibility to do Java code in pages.
Good goal, but the solution seems weird. The above should be simpler to
verify that they don't turn lazy.
BTW, the framework I outlined is servlet-template based. Strange though,
that post hasn't arrived yet. I will try to repost it.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
