On Thu, 18 Jun 2015 16:22:35 -0300, Casey Link
wrote:
Ugh, sorry. That was a failure on my part to correctly write the example
code for the email.
By the way, you haven't posted the template nor the corresponding code
(instead of just the event handler method names), so it's hard to know
On Thursday, June 18, 2015 04:01:43 PM Thiago H de Paula Figueiredo wrote:
> On Thu, 18 Jun 2015 14:47:51 -0300, Casey Link
> wrote:
>
> > Hi again,
>
> Hi!
>
> > Request event 'remove' (on component mypackage/MyPage) was not
> > handled; you must provide a matching event handler metho
On Thu, 18 Jun 2015 14:47:51 -0300, Casey Link
wrote:
Hi again,
Hi!
Request event 'remove' (on component mypackage/MyPage) was not
handled; you must provide a matching event handler method in the
component or in one of its containers.
Object onRemoveItem(Long id) {
Object o
Hi again,
Big thanks to Thiago and everyone else who answers questions on this list.
I have a standard pattern in my app an EventLink inside a zone that shuffles
items between lists. I based the code on the AJAX EventLink jumpstart [1]
The two eventlinks are "add" and "remove".
>From a full p
On Thu, 18 Jun 2015 11:22:01 -0300, Casey Link
wrote:
Hi,
Hi!
I have a TextField repeated many times that has a certain type,
validate, and class attributes set. Only the value and id changes.
Create a component with this TextField inside.
--
Thiago H. de Paula Figueiredo
Tapestry, Ja
Hi,
I have a TextField repeated many times that has a certain type, validate, and
class attributes set. Only the value and id changes.
What is the proper Tapestry way to prevent the repeating of all those options?
For example, if a css class changes, I want to set it in one place not a 100.
I