Hi Alex
It took me quite a while to debug and this is my understanding.
The loop uses a hidden field to store the 'value' parameter in the
form(using the encoder for converting it to a string) and later
retrieves the value before setting value of bound variables. The
hidden field also contains
Thanks for the info, Taha. Moving the zone out of the loop would allow
to properly process the textarea values but prevent the textareas from
being updated by the action links... A semi-ideal solution.
Is this something that is intentionally not supported by Tapestry for a
reason?
Regards,
Well I don't think it is intentional, if what I have inferred is
correct then it is a bug
An alternative will be not to use a zone, instead use your own
ajax/javascript calls.
regards
Taha
On Mon, Jun 27, 2011 at 6:55 PM, Alexander Rosemann
alexander.rosem...@gmail.com wrote:
Thanks for the
On Mon, 27 Jun 2011 10:38:12 -0300, Taha Hafeez tawus.tapes...@gmail.com
wrote:
Well I don't think it is intentional, if what I have inferred is
correct then it is a bug
An alternative will be not to use a zone, instead use your own
ajax/javascript calls.
I agree that this isn't an
Thanks for the hints and clarification. I was just wondering whether I
missed something obvious. I'll try to implement it using plain JS and
let you know how that went.
Many thanks though!
Regards,
Alex
On 27.06.2011 15:43, Thiago H. de Paula Figueiredo wrote:
On Mon, 27 Jun 2011 10:38:12
In order to build a json data source that I can inject into the page
using JavaScriptSupport I would like to know the real ids Tapestry
generates for the controls. Since the getter methods for the textarea
get called each iteration, I was wondering whether it is possible to get
access to the
Hi
@InjectComponent
private TextArea textArea;
void afterRender()
{
... textArea.getClientId();
}
regards
Taha
On Mon, Jun 27, 2011 at 9:57 PM, Alexander Rosemann
alexander.rosem...@gmail.com wrote:
In order to build a json data source that I can inject into the page using
Removing the zone surrounding the textarea fixes the save issue but of
course breaks the update functionality.
This is the code:
public class LoopWithZoneIssue {
private final Logger logger = LoggerFactory.getLogger(Feedback.class);
@Inject
private Request request;
@Property
Hi,
I asked this before but couldn't resolve the issue based on the
information that Taha forwarded me.
(http://tapestry.1045711.n5.nabble.com/loops-zones-and-encoders-td4425814.html#a4425945)
I have a loop that creates textareas within a form. Each textarea is
wrapped by a zone. Outside the
Hi
Whenever you use a zone in a loop, you should provide the javascript id
yourself. You can use the index to create a unique one
e.g.
t:zone t:id='textareaZone' id='textareaZone_${index}'
/t:zone
If you are using a non-ajax form, what is the use of zone here ??
regards
Taha
On Fri, Jun 24,
Hi Taha,
I should have put more thought in my example. The zone gets its unique
id and is updated by a set of actionlinks that I have omitted in my
previous example. This is the full one:
t:form
t:loop t:id=criteria value=currentCriteria source=criteria
encoder=cEncoder
t:loop
Can you share the code of the event handler for the action.
I think all the textareas are getting bound to the last object of the loop's
source
Regards
Taha
On Jun 24, 2011, at 7:35 PM, Alexander Rosemann alexander.rosem...@gmail.com
wrote:
Hi Taha,
I should have put more thought in
12 matches
Mail list logo
