> you are just limiting yourself with statemetns like this...
No. I only try to do the best with what things I already know ,and explore
under things that seems to be under used.
>I'm sure that WM allows you to do what you want.
Maybe
>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.
Not only, I also want to pass any objects from the servlet to the the
template. Such object could be any business object comming from a Databases
query, EJB, ... putting those objects in a hash table is a good idea, but
this can be achieve as well with FESI/ESP for example, that is wrapping a
java object in a Javascript
>Right...as one of the co-authors of it, we hope that you will contribute
>those types of objects back to us.
Yes, I certianly come back to you
>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.
Turbine seems very good design and programming. Some good and very simple
examples/tutorial could help
>Javascript is a HORRIBLE language. Netscape already made the mistake of
>trying to do this with a product and it failed miserably.
Maybe, but it's a fact that JAVASCRIPT is the prefered language at client
side, including the DOM reflection, liveconnect, ..
Manipulating HTML pages at server side through the DOM with Javascript could
help.
I am just thinking on line: but let's take the classical and simple example
of validating HTML forms: this could be done at client side with Javascript
handler, and I would like to do the same thing in the same way at server
side: that is : to build a DOM reflection of the HTML doc at the server
side, including input fields : this decision to put this at server or client
could be done elsewhere (something like a server side brower !!! maybe I am
saying something that makes no sense, XMLC seems to do things like that, but
the processing chain seems quite heavy)
I don't know excatly why Netscape failed. JS server side may not be the main
reason. They are maybe many other reasons for that : proprietary server
technology, not open source (now they try to come back with mozilla, but I
don't see anything since its launch - 2 or 3 years ago), lack of a clear
strategy :very poor support for Servlets in NS Server 3.xx (This was the
main reason I forgive NS server), now IPlanet try to fill this gap ???
BTW I am very happy with ORION and things such as ECS ;-)
___________________________________________________________________________
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
