> - we have to learn an other language (I think there are enough existing and
> powerfull technologies)
This is such an "old style" thing that keeps coming up. None of the
template languages actually make you learn a new "language". They may have
a certain way of doing something, but template languages aren't even a
language...I don't know how to describe it...but essentially, you are just
limiting yourself with statemetns like this...
> - we loose the power of JAVA:
> - object orientation, for example, can we have inheritence between
> WebMacro templates
I'm sure that WM allows you to do what you want.
> - WebMacro : I like the MVC model, where the model is your backend/business
> objects, the view is the template, and the Controler the servlet. It provide
> a clear separation between HTML and JAVA based stuff, between designers and
> programmers. But I don't like the PERL-like syntax (too lazy - where we
> loose the benefit of the strong object orientation - then why not use PHP or
> PERL for all things)
If you choose to use WM in the form of MVC, then the only portions of the
language that you need to know/use are essentially tag replacement syntax.
> - ECS : is a good and minimal starting point, but no model with it, only
> wraping HTML tags in java calls, However we can extend and add high level
> objects - this was the natural way when I first develop my first servlets
Right...as one of the co-authors of it, we hope that you will contribute
those types of objects back to us.
> - Turbine seems very good and is my prefered way of acheiving all
> requirements: MVC model, full JAVA, but the model seems too complex, too
> many constrainsts, difficult to learn, seems to impose some type of web
> servers, ....
It really isn't that complex considering all that you can get from it.
Take a look at Jyve <http://java.apache.org/jyve/>. It shows how simple it
can be to create a web application with very little overhead. Stuff like
security and user tracking is already taken care of for you.
Also, it is just a servlet. It can run in any servlet engine that supports
JSDK 2.0 or higher. I'm not sure where you get that it imposes some type
of web servers...
> In fact, my natural way of developing reusable servlets was to develop a
MVC
> model, where the servlet process incoming request and pass object to an ECS
> like data type, let say: MyPage. I can then refine MyPage class to develop
> the specific page of my application: query form, result pages, ....
That is exactly how Turbine works.
> But comming back to templates, and what about of Javascript Server Side ?
Javascript is a HORRIBLE language. Netscape already made the mistake of
trying to do this with a product and it failed miserably.
-jon
___________________________________________________________________________
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
