Thanx for pointing this out !
Ron
Mark Reynolds wrote:
Jesse pointed out that it should be target= instead of element= when the
thing being listened to is a Tapestry component (i.e., has a jwcid).
Apparently, element= is for html elements that aren't tapestry components.
If the problem you are
Jesse pointed out that it should be target= instead of element= when the
thing being listened to is a Tapestry component (i.e., has a jwcid).
Apparently, element= is for html elements that aren't tapestry components.
If the problem you are having is the same as mine (I think it might be) then
it
ok - I see there is a jira issue about this one...
Ron Piterman wrote:
Hi all -
I have a simlar scenario to the above post with the same name:
I call responseBuilder.updateComponent on the template-container of a
component with an @EventListener.
The component is being rendered but the java
Hi all -
I have a simlar scenario to the above post with the same name:
I call responseBuilder.updateComponent on the template-container of a
component with an @EventListener.
The component is being rendered but the javascript is not regenerated.
The usecase is as follows:
