Hmm, could you describe the situation a bit more. Are you using sessions or
not ?
It sounds like you are trying to break the encapsulation of the component.
Are you looking to have an object attached to the page which is accessed by
the component
and presented as a component getter ?
I can't
Hi Henrik!
Yes, I'm using sessions (comes from the authentication).
But again - I'm doing nothing special - I just want a component
to set attributes of a domain-object with values from a form. The
object is provided by a parameter.
Normally the attributes can be bound to the form-fields.
But as
@tapestry.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: component-binding/property side-effect (T4)
Hi Henrik!
Yes, I'm using sessions (comes from the authentication).
But again - I'm doing nothing special - I just want a component
to set attributes of a domain-object with values from a form
object using the constructor.
-Original Message-
From: Lukas Ruetz [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 01, 2006 8:26 AM
To: users@tapestry.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: component-binding/property side-effect (T4)
Hi Henrik!
Yes, I'm using sessions (comes from
]
Sent: Saturday, July 01, 2006 8:26 AM
To: users@tapestry.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: component-binding/property side-effect
(T4)
Hi Henrik!
Yes, I'm using sessions (comes from the
authentication).
But again - I'm doing nothing special - I just want
a component
]
Sent: Saturday, July 01, 2006 8:26 AM
To: users@tapestry.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: component-binding/property side-effect
(T4)
Hi Henrik!
Yes, I'm using sessions (comes from the
authentication).
But again - I'm doing nothing special - I just want
a component
