on 5/18/01 3:01 PM, "Eduardo Pelegri-Llopart"
<[EMAIL PROTECTED]> wrote:
> I didn't see any follow-up clarifying this but apologies if I missed it.
>
> JSP 1.2 has the notion of a TagLibraryValidator that is associated with
> a tag library. This can be used to portably validate different
> assertions on your JSP page. This could be used to, for example, check
> that some actions are nested within others, or that some portions of
> your JSP page conform in one way or another.
>
> A TagLibraryValidator can also be used to disable scriptlets.
Making it easy to disable scriptlets and breaking the specification are two
different things. It is part of the JSP specification to be able to use
scriptlets. By disabling them, you are encouraging people to break the
specification.
If people open their eyes and realize that the specification is
fundamentally flawed, then they will see that the alternative (and correct)
approach would be to remove scriptlets from the specification entirely.
If you go and do that, you are back at square one and might as well have
used another technology (which took this into consideration from the start)
in the first place.
Again, we are back to my point that simply taking an already terrible
technology (ASP) and trying to fit it into a Java model (JSP) is a really
brain damaged thing to do.
In order to fix the problems in ASP (and therefore JSP) one has two options:
1) Hack the exiting technology (JSP) until it kinda works. 2) Come up with
an alternative technology that took consideration of these points from the
start.
Clearly Sun chooses to take the approach of #1 because Sun would look like a
bunch of boneheads if they dropped JSP at this time. So, stick with what you
have and *try* to push it on people for as long as you can until someone
wakes up and realizes that what was pushed down their throat by Sun was a
stupid decision.
> On some of the other points in this thread:
>
> * Using XSTL for templating...
>
> Like Jon and some others, I think that XSTL is a bit too complicated
> (and memory expensive) to be my favorite templating mechanism. But it
> is a widely used as a transformation mechanism. Some thoughts on the
> role of XML, JSP & XSLT at
> http://java.sun.com/products/jsp/html/JSPXML.html
The humor in that article is that it all falls down as people realize that
they want to be able to take form input from something. If you notice, all
the arrows point towards the client. There are NO arrows that point from the
client towards the server. Once again, I'm not impressed because the
document doesn't address the larger vision of what people need to do in the
real world.
> * XML in Jasper...
>
> The JSP expert group has considered for a while adding a portable
> mechanism for transformations on a JSP page. Such a transformation
> would be defined as operating on the XML reprsetnation of a JSP page.
> I expect we will discuss again this feature for JSP 1.3, although there
> are no specific dates for that yet.
Yawn.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
