Hi Jeromy,
Many thanks for your thoughtful feedback on this issue.
Jeromy Evans wrote:
Personally, I never expose primitives as properties of an action
because null values are always legal over this interface. In the
special case of Boolean which can easily accidentally cause an NPE, I
alway
Giovanni Azua wrote:
Personally, I never expose primitives as properties of an action
because null values are always legal over this interface. In the
special case of Boolean which can easily accidentally cause an NPE, I
always make the getter return false if the value is null..
This validatio
Hi Jeromy,
Jeromy Evans wrote:
2nd, the parameters interceptor is called and sets properties of your
action. It cannot set primitives to null, so it does not write to
these properties.
3rd, the validation interceptors are executed. They cals the getters
of your action instance and observe th
Giovanni Azua wrote:
hi,
I provided declarative XML validation for a form where the action
would expose primitive type properties. The problem is that a
primitive type property left blank in the form would never be caught
as not provided by the "required" validation. The property would
inste
hi,
I provided declarative XML validation for a form where the action would
expose primitive type properties. The problem is that a primitive type
property left blank in the form would never be caught as not provided by
the "required" validation. The property would instead be set with the
def
5 matches
Mail list logo
