Thanks, I had there old tapestry-upload-5.3.7.jar pulled in by
tapestry5-jquery, so i`ve fixed it. Unfortunately without positive effect,
exception is still there.
Strange thing is that exception is comming from
org.apache.tapestry5.hibernate.modules.HibernateModule or at least it
So fixed, i had there also old version of tapestry-security. Million
thanks!
On Sun, 16 Nov 2014 09:22:23 +0100, Jan Fryblik jan.fryb...@ebrothers.cz
wrote:
Thanks, I had there old tapestry-upload-5.3.7.jar pulled in by
tapestry5-jquery, so i`ve fixed it. Unfortunately without
Geoff,
After some testing I can really see the benefits in how you achieve
this... One of my main prior misunderstanding was that the 'define' is
only run once (I thought it would be re-run each 'require'), making
similar to a 'static' object in some ways, in that the state is then
shared by
I've raised a JIRA for client-side pub/sub.
https://issues.apache.org/jira/browse/TAP5-2416
On 4 Sep 2014, at 5:57 pm, Geoff Callender
geoff.callender.jumpst...@gmail.com wrote:
In an AJAX request the server-side would have no way of knowing how many
subscribers there are within the page
Chris, It looks like the rule of thumb that I stated was wrong. I've just
used JavaScriptSupport#require in some AJAX event handlers.
Can someone explain under what circumstances we have to use
AjaxResponseRenderer#addCallback instead of JavaScriptSupport#require ?
Is it something to do with
Geoff,
AFAIK, JavascriptSupport is only available at render time and ajax render
doesn't start until after your event handler returns something. I think
it's because tapestry doesn't know what will need to be rendered yet.
For your second question, I think you can achieve what you want if you
