Is the solution (volatile=true) still valid for 5.0.17?
Or maybe any new clarifications?
Can not make my loop update source :(
TYA
On Thu, Oct 23, 2008 at 10:15 AM, Andy Pahne <[EMAIL PROTECTED]> wrote:
>
> I am trying to edit the properties of objects contained in a list by using
> a loop in
Quoting Andy Pahne <[EMAIL PROTECTED]>:
tapestryphoto schrieb:
I think you might find (as I did - see my 2nd original posting on
this issue) that the objects being updated in the loop are
different instances to the ones that are specified. It seems to be
a serialization problem (but tha
tapestryphoto schrieb:
I think you might find (as I did - see my 2nd original posting on this
issue) that the objects being updated in the loop are different
instances to the ones that are specified. It seems to be a serialization
problem (but that's a guess on my part - I don't know what the T
Jonathan Barker schrieb:
Well, that was fun. Sort of.
I did get it working by setting volatile="true" for the loop. It did leave
me scratching my head wondering about the interactions of Persist and
volatile.
Odd.
I like your approach. Works for me.
By the way: found another thread, wher
Hi,
From my experience, there is a "problem" for components which cause
events which are enclosed in a loop.
Tapestry will use the dom nesting for the component event url, and thus,
it is always the last (at least in my case) of the components which is
triggered by the event.
The solution is t
Quoting Andy Pahne <[EMAIL PROTECTED]>:
That were our web designers. But it worked that way in many other form
components. So I did not think about it any further.
Anyway, I tried . There's no difference in the
behaviour, regardless of which type of Submit is used.
I think you might find (
: Thursday, October 23, 2008 14:01
> To: Tapestry users
> Subject: Re: [T5] editing a looped list of objects' properties in a form
>
> Jonathan Barker wrote:
> > Perhaps you could post your full template and class. I don't see a
> submit
> > component so
Thiago H. de Paula Figueiredo wrote:
Em Thu, 23 Oct 2008 15:00:33 -0300, Andy Pahne <[EMAIL PROTECTED]> escreveu:
Jonathan Barker wrote:
id="search_accommodation_submit">${message:next-step}
Shoudn't you use a instead of a ? Or at
least a ?
That were our web designers. But
tapestryphoto wrote:
This looks similar to my problem (see both of my posts from a day or
so ago). It appears Loops in a Form do not update the properties.
Perhaps this is broken in Tapestry. I guess it must be a bug.
Unfortunately I'm not knowledgeable enough about Tapestry to provide
an an
Em Thu, 23 Oct 2008 15:00:33 -0300, Andy Pahne <[EMAIL PROTECTED]> escreveu:
Jonathan Barker wrote:
id="search_accommodation_submit">${message:next-step}
Shoudn't you use a instead of a ? Or at
least a ?
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer,
In my case an encoder would be useless, because the entities are new.
Their primary key would be null.
a.
tapestryphoto wrote:
My understanding is the "additional configuration" is in using an
encoder. If you have simple serializable objects (like I do) then it
should just encode them au
Jonathan Barker wrote:
Perhaps you could post your full template and class. I don't see a submit
component so I question what else has been omitted.
Jonathan
I omitted a few things that seemed unimportant to me. But here it is
complete, only some names obfuscated...:
http://tapestry.ap
My understanding is the "additional configuration" is in using an
encoder. If you have simple serializable objects (like I do) then it
should just encode them automagically in the form. If you have complex
objects then you need to write an encoder so only, say, object ids are
encoded in t
Perhaps you could post your full template and class. I don't see a submit
component so I question what else has been omitted.
Jonathan
> -Original Message-
> From: Andy Pahne [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 23, 2008 11:15
> To: Tapestry users
> Subject: [T5] editing a
It should work somehow, at least the documentation says so:
http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components/Loop.html
(at the very end of the page).
Quote "Tapestry form control element components (TextField, etc.) work
inside loops. However, so
This looks similar to my problem (see both of my posts from a day or
so ago). It appears Loops in a Form do not update the properties.
Perhaps this is broken in Tapestry. I guess it must be a bug.
Unfortunately I'm not knowledgeable enough about Tapestry to provide
an answer and I await so
16 matches
Mail list logo
