Hi Justin,
I am not sure I understand your point. Is the objection that in JSP
you have both scripting elements as well as custom tags? You could
say: "don't do that". Most development groups and/or individuals have
style guidelines that they enforce one way or another. For example
you can even use putback scripts that check your files don't have
scripting elements.
There is a different tackle on this: we can define a directive of a
JSP that means: "does not use scripting elements". Although you could
use this (specially with a project default value) as a stylistic tool,
I think the most useful function might be in assuring your ISP
provider that your JSP page will behave well. The ISP provider can
give you a list of JSP tag libraries you can use "safely", and then it
make some assumptions about your JSP page behavior.
----
I just went looking at webmacro.org and I am now more puzzled since
webmacro seems to have scripting elements. Justin, can you elaborate
your point a bit more?
Thanks!
- eduard/o
> Date: Wed, 3 Nov 1999 16:24:06 -0500
> From: Justin Wells <[EMAIL PROTECTED]>
> Subject: Re: Is JSP viable in a production environment
> The big difference is that the separation of logic from view is so
> critical that you really should have some architectural support for
> it. I don't think JSP provides that--it allows you to separate them,
> but only in the same way as assembly language programming can be
> structured--only if you behave.
> Template systems such as WebMacro and FreeMarker actually go a little
> further and enforce the separation architecturally. That makes it harder
> for you to get lazy and stick something where it doesn't belong.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
