Hi, [EMAIL PROTECTED] wrote:
ECS was created when servlets were the main technology for creating web pages. At that time, ECS was an alternative for hard-coding HTML in your servlets.
Times haven't changed that dramatically since then.
Now we have JSPs, XML to XLST, frameworks such as Cocoon, Tapestry, Wicket., MyFaces, etc With ECS you are still coding your HTML in your servlets which is a maintenance nightmare.
I disagree. The way of creating HTML through ECS is totally different from writing it down in its serialized form as you do in JSPs and XSLT. These serialized forms of HTML are dead code: You cannot easily re-use them or manipulate them, even in the same program, because they're text already. Approaches like ECS, or DOM via Javascript (to which it is fairly similiar), have a great advantage over the serialized approaches: You work object-oriented to build your HTML.
The development community has moved on to MVC frameworks.
You can use an MVC approach and still use ECS, that is not a contradiction. My bottom line is: ECS is rather simple and a bit low-level, but it still is a good way to create HTML. Georg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
