On Fri, 22 Jun 2012 02:12:57 -0300, Athneria, Mahendra
wrote:
Yes I thought about the same, just wanted to confirm if I assign the
object to null does it discarded from the Persist state?
Yes. That's what Howard said.
--
Thiago H. de Paula Figueiredo
-
...@gmail.com]
Sent: Thursday, June 21, 2012 8:45 PM
To: Tapestry users
Subject: Re: discard persistent field
Have you tried assigning them the value null?
On Thu, Jun 21, 2012 at 5:59 AM, Athneria, Mahendra <
mahendra.athne...@atos.net> wrote:
> Hi,
>
> ** **
>
> Is there an
http://tapestry.apache.org/persistent-page-data.html
The method discardPersistentFieldChanges() of ComponentResources will
> discard all persistent fields for the page, regardless of which strategy is
> used to store the property. This will not affect the page in memory, but
> takes effect for sub
Have you tried assigning them the value null?
On Thu, Jun 21, 2012 at 5:59 AM, Athneria, Mahendra <
mahendra.athne...@atos.net> wrote:
> Hi,
>
> ** **
>
> Is there any way through which I can discard the Object from
> PersistantConstant?
>
> ** **
>
> I got
> ComponentResources.*discar
Opened https://issues.apache.org/jira/browse/TAP5-455.
Kalle
On Mon, Jan 19, 2009 at 11:11 PM, Kalle Korhonen wrote:
> On Mon, Jan 19, 2009 at 10:37 PM, Ville Virtanen > wrote:
>
>>
>> It sounds like an addition that would be good to have when implementing
>> non-standard persistence strategie
On Mon, Jan 19, 2009 at 10:37 PM, Ville Virtanen
wrote:
>
> It sounds like an addition that would be good to have when implementing
> non-standard persistence strategies.
Thanks. Haven't heard from Howard but I'll open an issue anyway. I can get
this done without this enhancement, but it makes s
Hi,
It sounds like an addition that would be good to have when implementing
non-standard persistence strategies.
- Ville
Ps. I'm very interested in the results Kalle if you care to share? (Or
Kristian for that matter. Would it be possible to add a project to
tapestry.formos.com?)
Kalle Korh
Hey Kristian, thanks a lot for sending your project; it'll be interesting to
compare the implementations. Yes, of course there's a million different ways
of solving the problem but since the Tapestry architecture and services
offer a lot of functionality already for this, I tried to reuse most of i
hi kalle,
i've tried to solve this with another indirection :).
i encapsulate all conversation specific data in a ConversationContext
object.
if i want to invalidate a conversation i just remove this context.
i'm going to send you a zip with my experimental project
to your gmail address. maybe
