Would this also be the reason that I can't get an AjaxDirectLink to
behave correctly if it was in an updated component? Unfortunately I am
on Tap 4.0, so my fix may be more difficult if this is the case.
Richard Hoberman wrote:
Just a note to confirm that this does work with the 4.1.5 snapshot
Just a note to confirm that this does work with the 4.1.5 snapshot.
Andreas Andreou wrote:
Can you try it with a recent snapshot?
http://people.apache.org/maven-snapshot-repository/org/apache/tapestry/tapestry-framework/4.1.5-SNAPSHOT/
I think someone mentioned that something like this now shou
Thanks, Andreas.
The workaround works for me. I'll let you know how the snapshot turns out.
Richard
Andreas Andreou wrote:
Can you try it with a recent snapshot?
http://people.apache.org/maven-snapshot-repository/org/apache/tapestry/tapestry-framework/4.1.5-SNAPSHOT/
I think someone mentione
Can you try it with a recent snapshot?
http://people.apache.org/maven-snapshot-repository/org/apache/tapestry/tapestry-framework/4.1.5-SNAPSHOT/
I think someone mentioned that something like this now should work.
A workaround is to have the script you want to execute already in the
template and c
