> I mean..if all you had to do was put a bunch of <%= bean.getXXX() %>
> on a page, how hard is that to learn?
That was my argument in the early days of JSP. But <jsp:getProperty
name="foo"/> syntax won out as the recommended approach.
> As another fellow responded to you, I dont see much difference in
> the way WebMacro does things.
Although let's be clear that you've never tried WebMacro.
> But what if your template engine only runs on Windows, and you want
> to move to Unix?
Whoa! WebMacro, and all template engines I know about, are Pure Java
classes that work on top of the Servlet API. They work EVERYWHERE.
They're no different than the classes you write to support your
servlets. They don't integrate with the server because they don't need
to. They don't require vendor support anymore than your utility
classes. They work across all OS's and even on API 2.0 servers.
They even work with JServ (where JSP doesn't fully work).
> You cant. Not a very viable solution in my opinion.
I don't think you have a full understanding yet, based on the above.
Can I propose that instead of defending JSP without understanding the
alternative, you just go try the alternative for a while? I'm not
saying you'll like it, you probably won't, but then you can argue
based on facts and not impressions.
> The main reason people go to Java is its portability and ease of
> use
Well, templates are *more* portable.
> I cant say if a template engine such as WebMacro exists on multiple
> platforms or not, but I would imagine JSP/JavaBeans/Java has a much
> wider range of platforms and far more support in app servers and web
> servers.
Just the opposite.
> Actually, we did our own template engine via a servlet for a while.
> I can say this..it was 8 times slower than JSP is. That might be
> because we parse a "template" file replacing tokens with dynamic
> content in the servlet,
Yeah, repeated parsing is not the fastest way to go. :-)
> But, becuase my mindset is the way
> it is (Java engineer..dives into JSP to make our site much
> better, part of J2EE, etc), JSP seems a natural course of
> evolution for our site.
If you're the lone engineer and know Java, JSP can work fine for you.
Sounds like that's your position. It's often my position, and I still
prefer templates. Different strokes...
> I read some articles saying (Model 2)
> is more scalable in the future. I dont see how its any more or less
> scalable than Model 1.
How will you internationalize your Model 1 pages? You can't really.
You need Model 2 for that. How do you have your page display two
different error messages besides the success page, one for database
problems, one for form input problems? Model 2.
> Anyways..your still a java guru! ;)
Whew! :-)
-jh-
===========================================================================
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
