Am Freitag, 16. Januar 2009 18:13:49 schrieb dusty:
If you have the action can you use Reflection to step through the
properties and find the types that way?
I am using now BeanIntrospection + Parsing the failed Expression.
How can i get there without parsing the String and tokenizing the ognl
I want to customize the conversion error messages to be more special in cases
of wrong types.
Using a custom interceptor this is possible to do but lets say the map
contains an error for the field rule.date.
Thats the OGNL expression, telling me that getRule().setDate(Date a) failed,
because a
If you have the action can you use Reflection to step through the properties
and find the types that way?
Torsten Krah wrote:
I want to customize the conversion error messages to be more special in
cases
of wrong types.
Using a custom interceptor this is possible to do but lets say the
3 matches
Mail list logo