I'm sorry, that was not accurate.
The BeanEditForm component fires a prepare event. You can supply an
onPrepare() event handler method that can instantiate the bean as you
see fit. This bypasses the logic inside BeanEditForm to instantiate
the bean for you.
On Sun, Aug 17, 2008 at 6:12 AM, Howa
There's another option; you can contribute to the
ApplicationStateManager service, providing an ApplicationStateCreator
for your bean.
On Sun, Aug 17, 2008 at 2:04 AM, Andy Pahne <[EMAIL PROTECTED]> wrote:
>
> I have the same problem. Unfortunately I cannot add the @Inject annotation
> to the cla
I have the same problem. Unfortunately I cannot add the @Inject
annotation to the class in question, because it is a company wide
library and their maintainers rejected to add web related annotations to
the companies core business objects.
The only solution that came to my mind was using a
Thank YOU !! It solved problem.
Now i can proceed with my tapestry education :)
W dniu 16 sierpnia 2008 00:11 użytkownik Howard Lewis Ship
<[EMAIL PROTECTED]> napisał:
> This is some behavior that changes since the writing of the book.
>
> When the BeanEditForm instantiates a new Celeberty insta
This is some behavior that changes since the writing of the book.
When the BeanEditForm instantiates a new Celeberty 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 fo
Make sure Celebrity has a blank constructor and try again.
Educated guess, not 100% sure this is the issue.
Bob Heck
-Original Message-
From: ProAdmin Dariusz Dwornikowski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 15, 2008 15:49
To: users@tapestry.apache.org
Subject: Beanedit pro
