From: Don Brown [mailto:[EMAIL PROTECTED]
> [...]why we are using a template language at all.

My take on that was that the template language allowed more flexibility
at run-time and it allowed non-Java people to participate in custom
rendering of... uh... things.

> It would be faster because all but the more HTML-rich tags would be 
> generated in pure Java, bringing speed, tool support, and no new 
> syntax or EL to learn.

I wonder how often, in real life, non-programmers actually deal with
custom tags or would be the primary hands-on person in changing, say, a
Struts2 FreeMarker tag.

I do know that the JSP 2.0 custom tags are being used by non-hardcore
dev types, but a new system wouldn't preclude their use. I would want to
make sure, however, that it was "easy enough" to change the default
tags, especially for things like the form fields. I don't know how hard
it is to do that with Struts 2 right now; got pulled off my new project
for a few weeks :/

If the reality is that this rarely happens, and the classes for the
implementation of a tag can be loaded on-the-fly so I don't have to go
through a delay to see changes during development, then I really like
your proposal.

> Points 2 and 3 are what make this approach interesting.

+1

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to