On Tue, 05 Oct 2010 10:09:09 -0300, Michal Gruca <michalgr...@gmail.com>
wrote:
Hi all.
Hi!
After removing parametrized constructor,
error disappeared. It's bit odd IMHO.
That's documented behavior:
http://tapestry.apache.org/tapestry5.1/guide/appstate.html. This page is
for 5.1, but it should be the same for 5.2. Summary: Tapestry uses the
same logic for choosing a constructor used by Tapestry IoC. That page
shows you how to control the way you classes are instantiated.
Tapestry should be capable to
instantiate objects that have more than one constructor.
The problem here is: which constructor should be used? Tapestry IoC
chooses the one with the most parameters.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
