Done.
On 2/18/08, Jeromy Evans [EMAIL PROTECTED] wrote:
Thanks Don. Sorry, the confluence username is jeromyevans (with an o)
Don Brown wrote:
I tried, but I don't see your account. Could it be under something else?
Don
On 2/18/08, Jeromy Evans [EMAIL PROTECTED] wrote:
Can
Don Brown wrote:
I've cleared all but a couple issues out of Struts 2.1.1, so I think
we are ready for a release. The only kinda blocking issue is the
portlet tests failing, but that seems to have something to do with the
setup, not our portlet code, so we could even punt that one.
Any
I've been trying to catalog all of the cases where OGNL exists and where
it can be replaced. I'll sometime in the next few weeks to really work
on this and I'm hoping that we can replace OGNL from all developer
facing locations and completely standardize on EL. I think most folks
would be in
Please do:)
Don Brown wrote: I've cleared all but a couple issues out of Struts 2.1.1,
so I think we are ready for a release. The only kinda blocking issue is
the portlet tests failing, but that seems to have something to do with
the setup, not our portlet code, so we could even punt
Brian Pontarelli wrote:
I've been trying to catalog all of the cases where OGNL exists and where
it can be replaced.
Since different ELs specify different mechanisms to state this is an
expression to be evaluated, I wonder what we should do about the
delineating characters %{/} vs. ${/} vs.
Yeah, this is one of the frustrations that most beginners encounter and
that I'd really like to fix. I'd say it should be ${} or #{} so that it
is the same notation in JSPs, XML, etc. In fact, I would think that it
would make the most sense to follow the UEL convention such that ${} is
I started an Issues section and a Goals section to explicitly
identify the problem(s) that needs to be solved.
http://cwiki.apache.org/confluence/display/S2WIKI/OGNL+replacement
Brian Pontarelli wrote:
Yeah, this is one of the frustrations that most beginners encounter
and that I'd really
