For reference, there is a writeup of the main design ideas here:
http://webmacro.org/Servlet.html
which is long and not totally specific to WebMacro. My biggest problem
with JSP is that it does not architecturally enforce the separation
between presentation and processing. It gives you an MVC design pattern
you can follow, but nothing stops you from violating it.
You could violate it with WebMacro too, but it becomes much, much
more obvious that what you're doing is wrong.
I assume that most other template engines similarly enforce the
distinction, though some may not. So this is not just a WebMacro
benefit, though I'm always glad to see happy WebMacro users :-)
Justin
Quoting Robb Shecter ([EMAIL PROTECTED]):
> Doug Turner wrote:
> >
> > I'd like to hear your reasons for saying that JSP is *fundamentally*
> > flawed; my very limited experience with them have been positive, and I'd
> > like to get more input.
> >
>
> (I know this was posted a while ago, but...)
>
> I just got done checking out the various solutions out there for
> generating HTML from servlets, and chose webmacro. I spent a lot of
> time looking at JSP, especially because it's a Javasoft thing and
> widely supported, but I saw a couple of big, very practical problems
> with it:
>
> 1) I want to have a website where users have to log in. If possible,
> it should work like the Java Developer Connection, where a set of
> servlet-served pages can be protected. Once a user has logged in,
> they're sent back to the original protected page they requested.
>
> This is *trival* to do with normal servlet programming. Lots of
> articles have been written showing how, for example, with inheritance.
>
> This is *hard* to do with JSP. I think it's because of the
> control/execution model. I finally found an article at one of the
> servlet sites showing how, and it was nasty. A real hack with
> tricky/non-understandable code. Plus, a special #include and if/then
> block has to be put in each protected page.
>
> Webmacro uses the normal servlet execution model, and implementing
> this was very easy.
>
> To generalize: Authentication is orthogonal to the other processes,
> and JSP forces it to be highly coupled to everything else. Another
> orthogonal feature I want is transparent multi-lingual support. I
> imagine thatthis would also be nsty to cleay implement with JSP
> (especially if the authentication hack is there too!).
>
> 2) Webmacro's idea of *not* using HTML or XML-like tags is great. Any
> html editor can be used to edit the templates w/out problems.
>
> ----------
>
> And to the original question: Advanced Perl programmers use CGI.pm -
> basically what ECS is, as I understand it.
>
> - Robb
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
