Actually, no .. I cannot just use "JavascriptSupport.addScript"
everywhere I used to use "AjaxResponseRenderer.addCallback"
In XHR cases I get: UnknownValueException - "No object of type
org.apache.tapestry5.services.javascript.JavaScriptSupport is available
from the Environment."
I wonder w
Turned out this was because I was adding the script via
"ajaxResponseRenderer.addCallback" which used to be the recommended
approach.
JavascriptSupport now handles partial renders via "partialMode" (if you
look at the source).
Perhaps "ajaxResponseRenderer.addCallback" should be deprecated n
Feel free to answer on StackOverflow and I will give you the rep points.
http://stackoverflow.com/questions/16138055/mixin-script-added-in-afterrender-not-fired-for-xhr-requests
On 21/04/2013 4:05 PM, Paul Stanton wrote:
this is tapestry 5.3
On 19/04/2013 11:28 AM, Paul Stanton wrote:
Hi all,
this is tapestry 5.3
On 19/04/2013 11:28 AM, Paul Stanton wrote:
Hi all,
Can someone familiar with the mixin lifecycle please advise me:
I have a mixin which triggers some javascript from 'afterRender'. I do
this in 'afterRender' because I need the field's clientId to be
initialised.
It wo
