Hi
I have to agree with Jeremy. I would change the domain model and in
case i must do it in Wicket I will use I will try to configure a
Listener for a general purpose uppercase behavior
taha
On Thu, Mar 5, 2009 at 7:26 AM, James Carman
<jcar...@carmanconsulting.com> wrote:
> On Wed, Mar 4, 2009 at 6:29 PM, Jeremy Thomerson
> <jer...@wickettraining.com> wrote:
>> LOL! Nah - I would just change all the setters on every domain object to
>> be:
>>
>> public void setFoo(String foo) {
>> this.foo = foo == null ? null : foo.toUpperCase();
>> }
>>
>> Or, maybe I'd use AOP and build an aspect that could automatically intercept
>> calls to com.mydomain setters that take a single string argument and do the
>> upper-casing there!
>
> Instead of doing it on *all* single-string argument methods, you could
> annotate the parameters:
>
> public void setFoo(@Upcase String foo)
> {
> this.foo = foo;
> }
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
