mraible wrote:
I realize it might be a major effort, but this seems to be a pretty big deal
to me. Not for users that've already chosen Struts 2 as a web framework, but
for folks evaluating Java Web Frameworks. The fact that Struts 2 is the
*only* one that doesn't blow up on invalid properties ma
en Struts 2 as a web framework, but
for folks evaluating Java Web Frameworks. The fact that Struts 2 is the
*only* one that doesn't blow up on invalid properties makes it look pretty
bad for evaluations. It's kindof like the old blank page you'd sometimes get
with Tiles - you r
Jeromy Evans wrote:
mraible wrote:
I tried FreeMarker this morning and discovered that the problem
exists there
too. Grrr. I've experienced Struts 2 being eliminated as a web framework
candidate on a couple projects because of this. Kindof annoying.
So what do you really want? My guess
mraible wrote:
Following up months later as this has come up again now that 2.1 is close to
release. The current version does log messages for invalid properties, but
it doesn't blow up for invalid properties which is more of what I'm looking
for.
Hi Matt,
I'm not convinced that you really w
ethods into my action, so
>> it's not too bad.
>>
>> Matt
>
> -------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View
Good point. Feel free to open a S2 JIRA ticket that cross-references
XW-557 (since I'm not sure if its something we could do here or not)
-- and feel even more free to submit a patch!
As usual, we are short of active volunteers, and we can always use a
hand with the code!
-Ted.
On 9/6/07, mraibl
still fails silently. Any
>> >>> ideas how to get better error messages about invalid OGNL
>> expressions?
>> >>>
>> >>
>> >> I'll take that as a "no", it is not possible to get better error
>> >> messages. That's too
gt; >> I'll take that as a "no", it is not possible to get better error
> >> messages. That's too bad since it seems I get better type-safety and
> >> errors from scriptlets instead of OGNL.
> >>
> >> <%@ page
> >> import="org.
vlet,org.foo.bar.baz.enums.EnumCodec"
>> %>
>>
>> > var="q"><%=EnumCodec.URL.encode(SettingsServlet.ACTIONS.networkUpdates)%>
>>
>>
>>
>> VS:
>>
>> > value="url(@[EMAIL PROTECTED]).q(@[EMAIL PROTECTED](
lue="url(@[EMAIL PROTECTED]).q(@[EMAIL PROTECTED](@[EMAIL PROTECTED]))"/>
>
> The framework I'm looking to migrate to Struts 2 has the ability for it's
> EL to read from imported Statics - a pretty cool feature IMO.
>
> ${url(pageBean.MAPPING.SETTINGS
LET).q(EnumCodec.URL.encode(SettingsServlet.ACTIONS.networkUpdates))}
Matt
--
View this message in context:
http://www.nabble.com/How-can-I-tell-Struts-2-to-throw-log-exceptions-for-invalid-OGNL-Expressions-tf4100102.html#a12282397
Sent from the Struts - User mailing list archive at Nabble.
y:
I've tried turning up the logging for org.apache.struts2,
com.opensymphony.xwork2 and ognl - but it still fails silently. Any ideas
how to get better error messages about invalid OGNL expressions?
Thanks,
Matt
--
View this message in context:
http://www.nabble.com/How-can-I-tell-St
12 matches
Mail list logo
