not so stretched for time. Thanks again.
Regards,
Jim.
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 23 September 2010 17:27
To: Tapestry users
Subject: Re: PropertyEditContext not available from Environment
On Thu, 23 Sep 2010 12:50:47 -0300,
On Thu, 23 Sep 2010 12:50:47 -0300, Jim O'Callaghan
wrote:
Thiago,
Hi!
Are you saying the I can use to get
around the problem?
Yes.
Do I just build a list of PropertyOverrides in the page class for that,
and does it override all other overrides that the grid normally provides
by
[mailto:thiag...@gmail.com]
Sent: 23 September 2010 14:11
To: Tapestry users
Subject: Re: PropertyEditContext not available from Environment
On Thu, 23 Sep 2010 09:25:14 -0300, Jim O'Callaghan
wrote:
> Thanks Thiago. I'll file a JIRA after I come up with a workaround. I
>
On Thu, 23 Sep 2010 09:25:14 -0300, Jim O'Callaghan
wrote:
Thanks Thiago. I'll file a JIRA after I come up with a workaround. I
would have thought this was a common enough use case, an editable custom
field in a grid.
I was talking about creating a component that does that, not using t
: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 23 September 2010 13:03
To: Tapestry users
Subject: Re: PropertyEditContext not available from Environment
On Thu, 23 Sep 2010 07:22:43 -0300, Jim O'Callaghan
wrote:
> Thanks Thiago. Can you clarify one last thing for me
On Thu, 23 Sep 2010 07:22:43 -0300, Jim O'Callaghan
wrote:
Thanks Thiago. Can you clarify one last thing for me. I had a look at
the sources you mentioned and am wondering if I have to create a
PropertyEditContext from scratch before pushing it to the environment,
or is there somewhere
good bit of code to have to duplicate per custom component?
Regards,
Jim.
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 23 September 2010 01:44
To: Tapestry users
Subject: Re: PropertyEditContext not available from Environment
On Wed, 22 Sep 2010
On Wed, 22 Sep 2010 19:48:08 -0300, Jim O'Callaghan
wrote:
Thanks for the reply Thiago. Could you give me a pointer on where / how
in the cycle to push and then pop the PropertyEditContext into / out of
the Environment, or point to any resource I could work through as an
example? A bit
: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 22 September 2010 23:44
To: Tapestry users
Subject: Re: PropertyEditContext not available from Environment
On Wed, 22 Sep 2010 19:20:30 -0300, Jim O'Callaghan
wrote:
> No object of type org.apache.t
On Wed, 22 Sep 2010 19:20:30 -0300, Jim O'Callaghan
wrote:
No object of type org.apache.tapestry5.services.PropertyEditContext is
available from the Environment
When you're using BeanEditor/BeanEditForm, they push the appopriate
PropertyEditContext into the Environment. Grid pushes a
Pr
I have a custom data type that I am displaying / updating successfully in
beanDisplays and beanEditForms, after making BeanBlockContributions for edit
and display, and also using a CustomPropertyEditor that defers
environment.pop(PropertyEditContext.class) until after rendering is
complete. Recent
11 matches
Mail list logo
