There are two discussions going on here that could probably be split:
1. OGNL vs. JUEL
2. Taglibs
#1 has already come up a number of times and I believe that there is
enough support to move the JUEL plugin forward and start removing OGNL
once a roadmap is clear. The wiki page Dale pointed to is the best place
to add your thoughts to the roadmap.
#2 This has also come up before, but just so folks know... there is very
little stopping anyone from implementing their own taglib. JCatapult is
going to do this and I would think it would make sense to have a few
others out there. Remember that the taglib is a distinct component and
not necessary to use the core. It has very few side-effects and is
mostly pulling data and generating HTML. Rarely does it effect
application state. In fact, some have argued the current tags in core
should be a plugin.
Perhaps two new threads should continue this discussion.
-bp
Felipe Rodrigues wrote:
But we have that situation in most pages that we develop. Since the
Struts tags are not all encompassing, we must supplement our framework
with other tags, like DisplayTag and other standard JSP tags. So,
allowing the full use of JUEL (or JSTL EL) in the Struts tags,
actually reduces confusion since it allows us to use one EL for an
entire page.
Yes, but OGNL is a base for Struts2 stack. And EL is only removed because of
the security problem.
I'm not saying that use of EL is bad.
We can't stop the confusion without either expanding the Struts taglib
so that you would never need an outside tag or convert all the other
tag libraries to OGNL. I don't see either of these as being possible.
It is a good point. But again, the position of Struts leaders is to show
that Struts2 is secure. Show that you should not use EL in Struts2 without
concerns, because Struts2 tags evaluates everything as OGNL after the EL
evaluation.
So, I still believe this thread should be talking about an alternate build
of Struts2, or at least an open documentation about how to enable EL to be
used and telling the risks to be taken for that.
Chris Pratt wrote:
On Thu, Mar 6, 2008 at 7:51 AM, Felipe Rodrigues <[EMAIL PROTECTED]>
wrote:
Your suggestion for question 1 is good, since we have more description
on
struts documentation.
The 2 point is the most important, from my view.
Use JSP EL in Struts2 tag is not a best pratice. Match these kind of
languages could make the code confuse to be maintained. Sometimes you
use
OGNL, othertimes you use JSTL EL.
But we have that situation in most pages that we develop. Since the
Struts tags are not all encompassing, we must supplement our framework
with other tags, like DisplayTag and other standard JSP tags. So,
allowing the full use of JUEL (or JSTL EL) in the Struts tags,
actually reduces confusion since it allows us to use one EL for an
entire page.
We can make this stop now, buy forcing people to use OGNL or leave it
possible to use and keep trying to make them understand that it is a bad
pratice.
We can't stop the confusion without either expanding the Struts taglib
so that you would never need an outside tag or convert all the other
tag libraries to OGNL. I don't see either of these as being possible.
I think lot of people can say that match it is not a bad pratice, but...
well, somebody have to decide it.
You can call it bad practice if you want, but I prefer JSTL EL to OGNL
since it is ubiquitous, powerful, consistent and much easier to train
Web Developers to use.
But then again, that's just one man's opinion.
(*Chris*)
---------------------------------------------------------------------
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]
