Hi there,
back in the old days I used to use GWT alot in conjunction with
Tapestry. Nowadays it would be fine to develop using JS at the Client side
and I want to use Tapestry at the backend.
I would love to use something like socket.IO directly within the
JS-client-code so I investigated the
Same here. Any ideas why does that happen?
On Sun, Jun 24, 2012 at 9:24 PM, Simon Raveh wrote:
> Hi All,
>
> We continue getting this error, I can't reproduce it on my dev system.
> This only happens on a none ajax requests.
> Any help is welcome.
>
> Thanks,
> Simon
>
> From: Dongmei Cao mail
On Aug 15, 2013, at 12:51 PM, Thiago H de Paula Figueiredo
wrote:
> Your Java code looks ok. Could you please post your JavaScript code that
> is invoked by the addInitializerCall() call? It may be choking on the
> query string.
>
I don't want to waste anyones time. Removing @PageActivationCo
On Aug 15, 2013, at 12:51 PM, Thiago H de Paula Figueiredo
wrote:
> Your Java code looks ok. Could you please post your JavaScript code that
> is invoked by the addInitializerCall() call? It may be choking on the
> query string.
>
Sorry I forgot it.
(function ($) {
T5.extendInitializers(
Your Java code looks ok. Could you please post your JavaScript code that
is invoked by the addInitializerCall() call? It may be choking on the
query string.
--
Thiago H. de Paula Figueiredo
-
To unsubscribe, e-mail: users-un
Our pages all extend a common layout, that has a simple value that we update
every minute with an ajax call.
The handler is in the component class for the layout, and is very simple:
public JSONObject onUpdateAlertCount() {
return request.isXHR() ? new JSONObject("alertCount", getAle