Em Thu, 02 Apr 2009 13:49:59 -0300, nillehammer
escreveu:
In this case, you don't want that behavior. You surely want BeanEditForm
to instantiate via the public no-arguments constructor.
Another option is to use the prepare event to instantiate the object
yourself.
--
Thiago H. de Paula
no problem, i like the past :)
why can't it cope with the enum parameter constructor? it works fine
with the String parameter type. itself tapestry should know how to build
an enum instance (for displaying the combo-box it does correctly).
Or is there a finite list which "parameter-types" can
Sorry to have messed up the thread. My local clock was wrong
nillehammer schrieb:
> When the BeanEditForm instantiates a new Model instance, it now uses the
> same code that instantiates service implementations (and injects
> dependencies). By default, Tapestry will find the constructor with the
>
When the BeanEditForm instantiates a new Model instance, it now uses the
same code that instantiates service implementations (and injects
dependencies). By default, Tapestry will find the constructor with the
most parameters for this purpose, and will attempt to match each
parameter to a service. T
