If you don't want to learn anything new, why stop in the middle at
JXP? Just use java itself. Then there's no new syntax (we'll ignore
the fact that java syntax is still evolving...) and no new API (again
ignoring the fact that those change too) that can often take longer to
grok than a new syntax.
Sarcasm, aside, lines 2 thru 5 of the example script at
(http://jxp.sourceforge.net) are the new, non-java, not-quite-jsp
syntax of JXP. Don't kid yourself. There is both new syntax and new
API here. It may be minimal, but it's there. It has to be,
otherwise, it's just an incomplete java interpreter with some new APIs
built in. You might as well use something with more momentum and
support, like Groovy.
The syntax of template languages like Velocity or Freemarker is
intentionally designed to be simple and quick to learn. Yeah, things
like try-catch or synchronized blocks would probably involve a lot of
complexity in such new template languages were they even possible, but
there's good reasons for making such things difficult/impossible in a
templating language. Also, the lack of an EL in JXP may simplify the
syntax, but at the cost of a lot more keystrokes. There's a reason
JSP, Velocity, Freemarker, and friends all have those.
On 10/17/06, Mike B <[EMAIL PROTECTED]> wrote:
Hi Guys,
I am simply responding because we have been using JXP for about 7 months
now..
We are currently using JXP for our web component templates. It has worked out
fairly well. We actually started out using FreeMarker, but did not like the
idea of learning a new syntax just for simple templating. Sure... its not
that big of a deal, but what is the value add of learning additional syntax to
do something you could do in Java (even easier).
We also felt that JXP was easier to work with front to back. We were up and
running in a couple of hours. Its nice to have the ability to write Java code
in your templates. We never have much, but for the small sections that need
it, it comes in handy.
It would be great to see some others take interest in the project. I feel the
over all benefits of having a popular and well supported template engine that
has a JSP like syntax is a no-brainer.
Some key reasons:
- You get mainstream tool support for free.
- You get a template engine with a familiar syntax
- It makes for easy migration of JSP artifacts to templates (which are no
longer bound to a JSP/Servlet container).
Just some 3rd party thoughts.....
Cheers,
Struts Action 2 / WW User
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=46468&messageID=94261#94261
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
