You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Jonas <ba...@gmail.com> on 2007/09/11 11:05:08 UTC
User-defined variables in ConversionException
Hi,
wouldn't it make sense that you could set arbitrary variables
on a ConversionException that would also be set on the ValidationError
created in FormComponent#convertInput()?
Currently, you can set the resource key that should be used for the
error message, but you're limited to the few variables defined in
FormComponent#convertInput().
I know I could override convertInput(), but I think user-defined variables
would be a more elegant solution.
What do you think?
cheers,
Jonas
Re: User-defined variables in ConversionException
Posted by Jonas <ba...@gmail.com>.
I created https://issues.apache.org/jira/browse/WICKET-961
which also contains a patch against current trunk.
cheers,
Jonas
On 9/12/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> Nope go ahead. If someone does mind, the issue is quickly closed ;)
>
> Martijn
>
> On 9/12/07, Jonas <ba...@gmail.com> wrote:
> > No opinions on that one?
> > So, would anyone mind if I create a 'New Feature' Issue
> > in JIRA?
> >
> > On 9/11/07, Jonas <ba...@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > wouldn't it make sense that you could set arbitrary variables
> > > on a ConversionException that would also be set on the ValidationError
> > > created in FormComponent#convertInput()?
> > > Currently, you can set the resource key that should be used for the
> > > error message, but you're limited to the few variables defined in
> > > FormComponent#convertInput().
> > > I know I could override convertInput(), but I think user-defined
> variables
> > > would be a more elegant solution.
> > >
> > > What do you think?
> > >
> > > cheers,
> > > Jonas
> > >
> >
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-beta3 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: User-defined variables in ConversionException
Posted by Martijn Dashorst <ma...@gmail.com>.
Nope go ahead. If someone does mind, the issue is quickly closed ;)
Martijn
On 9/12/07, Jonas <ba...@gmail.com> wrote:
> No opinions on that one?
> So, would anyone mind if I create a 'New Feature' Issue
> in JIRA?
>
> On 9/11/07, Jonas <ba...@gmail.com> wrote:
> >
> > Hi,
> >
> > wouldn't it make sense that you could set arbitrary variables
> > on a ConversionException that would also be set on the ValidationError
> > created in FormComponent#convertInput()?
> > Currently, you can set the resource key that should be used for the
> > error message, but you're limited to the few variables defined in
> > FormComponent#convertInput().
> > I know I could override convertInput(), but I think user-defined variables
> > would be a more elegant solution.
> >
> > What do you think?
> >
> > cheers,
> > Jonas
> >
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: User-defined variables in ConversionException
Posted by Jonas <ba...@gmail.com>.
No opinions on that one?
So, would anyone mind if I create a 'New Feature' Issue
in JIRA?
On 9/11/07, Jonas <ba...@gmail.com> wrote:
>
> Hi,
>
> wouldn't it make sense that you could set arbitrary variables
> on a ConversionException that would also be set on the ValidationError
> created in FormComponent#convertInput()?
> Currently, you can set the resource key that should be used for the
> error message, but you're limited to the few variables defined in
> FormComponent#convertInput().
> I know I could override convertInput(), but I think user-defined variables
> would be a more elegant solution.
>
> What do you think?
>
> cheers,
> Jonas
>