Re: Google 4.4 latest plugin update for Eclipse.

2014-11-06 Thread Jens

>
> *B*) It still only has an option for GWT 2.6.0 SDK as part of the 
> downloadable SDKs?
>
> Is this intentional? I was expecting 2.6.1 as being an option under the 
> SDK list.
>

I think no new GWT SDK has been pushed to the update site for whatever 
reason. However you can simply download the SDK zip file from 
http://www.gwtproject.org/versions.html . Just unzip it and manually add 
the folder as SDK in the Eclipse settings. 

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Problems upgrading Google Plugin for Eclipse

2014-11-06 Thread Thad Humphries
I haven't been able to install the "Google Plugin for Eclipse 
4.4 3.8.0.v201410302155-rel-r44" update. I'm told "Insufficient privileges 
to apply this update". I've no idea why. Everything in 
the /Applications/eclipse directory is owned by me, as is everything in the 
.metadata directories of my workspaces. Even after removing all *.lock 
files and restarting Eclipse, it's still not working. Any ideas? Maybe some 
file(s) I should edit or delete. (I think before I blow everything away and 
reinstall 4.4 from scratch, I'll wait for an update that includes GWT 
2.7.0.)

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Re: Server Push

2014-11-06 Thread Alain Ekambi
Errai is the thing you want to use :)

2014-11-06 21:08 GMT+01:00 Peter Donald :

> Hi,
>
> On Thu, Nov 6, 2014 at 12:07 AM, Marcel K  wrote:
>
>> Which framework for Server Push do you recommend, since Atmosphere
>> doesn't seem to work with GWT 2.7.0?
>>
>
> It sort of depends on your environment and what your underlying platform
> supports. Below is a response I made to another similar question on the
> mailing list.
>
> In short if you can use latest JEE or jersey then I would recommend that
> you use
> * built-in web sockets (
> https://github.com/realityforge/gwt-websockets-example/blob/master/src/main/java/org/realityforge/gwt/websockets/example/server/ChatServer.java
> )
> * addon support for EventSource/ServerSent events (
> https://github.com/realityforge/gwt-eventsource-example/blob/master/src/main/java/org/realityforge/gwt/eventsource/example/server/
> )
> * Servlet 3 async services for long polling (
> https://github.com/realityforge/gwt-webpoller-example/tree/master/src/main/java/org/realityforge/gwt/webpoller/example/server
> )
>
> We use all three in our server push apps with GWT clients.
>
> HTH
>
>
> On Fri, Oct 31, 2014 at 5:22 AM, Peter Donald 
>  wrote:
>
>> Hi,
>>
>> We have built several systems like this where we want to push data to
>> clients from the server. The client is responsible for subscribing to a
>> channel possibly with filters in place. Rather than use GWT-RPC we have
>> tended to move to using raw messages that are typically json blobs. We have
>> used 4 basic strategies depending on the clients supported and the
>> application requirements. The strategies are;
>>
>> 1. WebSockets
>> 2. Server-Sent Events
>> 3. Long polling
>> 4. Periodic Polling
>>
>> I had a poke around and found a good stack overflow answer to this (See
>> [1])
>>
>> When we faced the same issues, we ended up putting together a couple of 
>> libraries
>> to help with in GWT.
>>
>> * websockets: https://github.com/realityforge/gwt-websockets
>> * Server-sent Events: https://github.com/realityforge/gwt-eventsource
>> * Polling: https://github.com/realityforge/gwt-webpoller (Warning this
>> API is not yet at 1.0 status)
>>
>> The tricky part is actually managing the channels and messages sequencing
>> in each channel but we never got arounf to releasing our code for that part
>> of the problem.
>>
>> HTH
>>
>> [1]
>> http://stackoverflow.com/questions/11077857/what-are-long-polling-websockets-server-sent-events-sse-and-comet
>>
>
> --
> Cheers,
>
> Peter Donald
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Alain Ekambi

Co-Founder

Ahomé Innovation Technologies

http://www.ahome-it.com/ 

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Re: Server Push

2014-11-06 Thread Peter Donald
Hi,

On Thu, Nov 6, 2014 at 12:07 AM, Marcel K  wrote:

> Which framework for Server Push do you recommend, since Atmosphere doesn't
> seem to work with GWT 2.7.0?
>

It sort of depends on your environment and what your underlying platform
supports. Below is a response I made to another similar question on the
mailing list.

In short if you can use latest JEE or jersey then I would recommend that
you use
* built-in web sockets (
https://github.com/realityforge/gwt-websockets-example/blob/master/src/main/java/org/realityforge/gwt/websockets/example/server/ChatServer.java
)
* addon support for EventSource/ServerSent events (
https://github.com/realityforge/gwt-eventsource-example/blob/master/src/main/java/org/realityforge/gwt/eventsource/example/server/
)
* Servlet 3 async services for long polling (
https://github.com/realityforge/gwt-webpoller-example/tree/master/src/main/java/org/realityforge/gwt/webpoller/example/server
)

We use all three in our server push apps with GWT clients.

HTH


On Fri, Oct 31, 2014 at 5:22 AM, Peter Donald 
 wrote:

> Hi,
>
> We have built several systems like this where we want to push data to
> clients from the server. The client is responsible for subscribing to a
> channel possibly with filters in place. Rather than use GWT-RPC we have
> tended to move to using raw messages that are typically json blobs. We have
> used 4 basic strategies depending on the clients supported and the
> application requirements. The strategies are;
>
> 1. WebSockets
> 2. Server-Sent Events
> 3. Long polling
> 4. Periodic Polling
>
> I had a poke around and found a good stack overflow answer to this (See
> [1])
>
> When we faced the same issues, we ended up putting together a couple of 
> libraries
> to help with in GWT.
>
> * websockets: https://github.com/realityforge/gwt-websockets
> * Server-sent Events: https://github.com/realityforge/gwt-eventsource
> * Polling: https://github.com/realityforge/gwt-webpoller (Warning this
> API is not yet at 1.0 status)
>
> The tricky part is actually managing the channels and messages sequencing
> in each channel but we never got arounf to releasing our code for that part
> of the problem.
>
> HTH
>
> [1]
> http://stackoverflow.com/questions/11077857/what-are-long-polling-websockets-server-sent-events-sse-and-comet
>

-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Google 4.4 latest plugin update for Eclipse.

2014-11-06 Thread Michael Joyner
I've just updated to the latest version of the plugin for Eclipse and 
noticed two things:


*A*) There is now a "Run as SDM" for GWT enabled projects. It seems to 
work fine with source code pulled from other projects via linked folders 
which is nice.


Because of the way our Servlet is configured, it doesn't work inside of 
Jetty. So we just tell Eclipse to start the superdevmode followed up by 
running it on Tomcat and sdm is working fine.


*B*) It still only has an option for GWT 2.6.0 SDK as part of the 
downloadable SDKs?


Is this intentional? I was expecting 2.6.1 as being an option under the 
SDK list.


-Mike

--
You received this message because you are subscribed to the Google Groups "Google 
Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Re: GWT Cross Site Iframe Linker and Script Tags

2014-11-06 Thread Etienne Lacazedieu
Well, it was a Code Splitting problem.

Both SuperDevMode and DevMode works fine with the new linker.





Le mercredi 5 novembre 2014 23:21:22 UTC+1, Etienne Lacazedieu a écrit :
>
> Hi,
>
> I'm preparing a big switch (GWT2.3 to 2.6.1, which may change to 2.7.0 
> depening on the final release date), and I'm having trouble with the 
> xsiframe linker.. I have no problems with adding script> tags in the HTML 
> file.
>
> Actually, I wrote a linker (a subclass of CrossSiteIframeLinker), which 
> outputs the list of JS files to a properties file.
>
> On the server side, a class reads this file to add 

Exception thrown by XMLHttpRequest

2014-11-06 Thread Krzysztof Pater
Hi All,

I am developing an application using GWT in version 2.5.1.

Few days ago we found in our logs that there is a huge amount of exceptions 
(few per second!!!) that look as follows:

Nov 5, 2014 6:00:45 PM com.google.gwt.logging.server.
RemoteLoggingServiceUtil logOnServer
SEVERE: (NS_ERROR_NOT_INITIALIZED) : 
com.google.gwt.core.client.impl.SerializableThrowable$ThrowableWithClassName
: (NS_ERROR_NOT_INITIALIZED) : 
 at Unknown.ZHe(StackTraceCreator.java:174)
 at Unknown.WFe(StackTraceCreator.java:508)
 at Unknown.IHf(Exceptions.java:29)
 at Unknown.pIb(XMLHttpRequest.java:164)
 at Unknown.OMe(RequestBuilder.java:411)
 at Unknown.anonymous(XMLHttpRequest.java:351)
 at Unknown.gHe(Impl.java:189)
 at Unknown.jHe(Impl.java:243)
 at Unknown.anonymous(Impl.java:70)

At least in two cases the problem happened when the application was used 
from Mozilla Firefox web browser. To stop that, it was not enough to close 
the browser, but also to kill process from the Task Manager. But I am not 
sure if it couldn't be triggered also by another browser.

I also found this comment in the com.google.gwt.http.client.Request class, 
method cancel():

/*
 * There is a strange race condition that occurs on Mozilla when you 
cancel
 * a request while the response is coming in. It appears that in some 
cases
 * the onreadystatechange handler is still called after the handler 
function
 * has been deleted and during the call to XmlHttpRequest.abort(). So we
 * null the xmlHttpRequest here and that will prevent the
 * fireOnResponseReceived method from calling the callback function.
 * 
 * Setting the onreadystatechange handler to null gives us the correct
 * behavior in Mozilla but crashes IE. That is why we have chosen to 
fixed
 * this in Java by nulling out our reference to the XmlHttpRequest 
object.
 */

I don't have knowledge about how requests are working but I am wondering if 
new releases of Mozilla Firefox didn't cause that above solution doesn't 
work in some cases. 

Do you have an idea what is the source of the problem and could you please 
give us any advice how to solve this issue or maybe some workaround how to 
deal with it?

Thank you in advance!

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Re: Development Mode will not be supported in Firefox 27+

2014-11-06 Thread Jens

>
> I'm using IntelliJ...I'd like to hear if/how IntelliJ can do this too.
>

With the released IntelliJ 14 things are a bit easier.

- Create a new GWT run configuration and select "User Super Dev Mode" and 
at the bottom "with JavaScript debugger". 
- IntelliJ will automatically generate a JavaScript debugger run 
configuration. Open that run configuration and you should see your GWT 
project directory tree. In that tree navigate to your source folder (src or 
src/main/java) and double click on the "Remote URL" column next to it. The 
remote URL is where IntelliJ will download source map files from so you 
should paste in something 
like http://127.0.0.1:9876/sourcemaps/.

Now launch the GWT SDM run configuration which should also automatically 
launch the JavaScript Debug configuration. Chrome should now tell you that 
IntelliJ is debugging your site (you may need to install the LiveEdit 
Chrome extension) and you should be able to set break points in your Java 
code and step through the code from within IntelliJ.

Sometimes when you hit a break point the source map file isn't ready yet in 
IntelliJ (seems like a timing problem) and you see the pure JavaScript. But 
once you do the first "step over" IntelliJ should switch to the Java source 
by using source map information. Overall it works pretty well.

But keep in mind that fields and expressions in conditional break points 
are still all JavaScript. You are not debugging Java!

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Re: Unable to use Elemental

2014-11-06 Thread Nyamath Ulla Khan
I was facing the same problem and solved by reading this link.Please follow 
this link 
*http://stackoverflow.com/questions/4550483/gwt-test-unable-to-find-sample-gwt-xml-on-your-classpath
 *

On Monday, 27 October 2014 21:42:24 UTC+5:30, Manuel Carrasco wrote:
>
> Have you tried to run your code in superdev-mode or compiled ?
>
> On Sun, Oct 26, 2014 at 9:01 PM, Steve > 
> wrote:
>
>> It seems i can no longer instantiate objects as i was doing before since 
>> using Elemental.
>>
>> I'm getting errors on this line for some reason:
>>
>> Image imgPlay = new Image("img/Blue_Play_Button_Pressed_Down.svg");
>>
>> I tried changing it to Image imgPlay = new Image(); but got the same 
>> error. This works fine when i'm not referencing Elemental.
>>
>> The DevMode console displayed the following:
>>
>> Caused by: com.google.gwt.core.client.JavaScriptException: (String) : 
>> Invoking an instance method on a null instance
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>> at 
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> at 
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>> at 
>> com.google.gwt.dev.shell.ModuleSpace.createJavaScriptException(ModuleSpace.java:80)
>> at 
>> com.google.gwt.dev.shell.ModuleSpace.createJavaScriptException(ModuleSpace.java:64)
>> at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:60)
>> at 
>> com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
>> at 
>> com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:338)
>> at 
>> com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:219)
>> at 
>> com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
>> at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:576)
>> at 
>> com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid(ModuleSpace.java:304)
>> at 
>> com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.java:107)
>> at 
>> com.google.gwt.user.client.impl.DOMImplStandard.initEventSystem(DOMImplStandard.java)
>> at 
>> com.google.gwt.user.client.impl.DOMImpl.maybeInitializeEventSystem(DOMImpl.java:181)
>> at 
>> com.google.gwt.user.client.impl.DOMImplStandard.sinkEvents(DOMImplStandard.java:216)
>> at com.google.gwt.user.client.DOM.sinkEvents(DOM.java:1361)
>> at com.google.gwt.user.client.Event$.sinkEvents(Event.java:597)
>> at 
>> com.google.gwt.user.client.ui.Image$UnclippedState.(Image.java:376)
>> at com.google.gwt.user.client.ui.Image.(Image.java:510)
>> at 
>> com.example.elem.client.ElementalDemo.onModuleLoad(ElementalDemo.java:31)
>>
>>
>> On Sunday, 26 October 2014 19:32:54 UTC, Jens wrote:
>>>
>>> Please could someone share any thoughts?

>>>
>>> Putting gwt-elemental.jar on class path and inheriting 
>>> elemental.Elemental is fine and it should work.
>>>
>>> When you see "failed to load the module" you usually see the reason in 
>>> the DevMode console. We can't guess reasons.
>>>
>>> -- J.
>>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google Web Toolkit" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-web-toolkit+unsubscr...@googlegroups.com .
>> To post to this group, send email to google-we...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


java.util.Date clientside incorrect timezone

2014-11-06 Thread Stepan
hello everyone!

I have a strange problem with dates. when i work in dev mode all is ok, but 
when i work in web mode i have problems on client side. 

i have this code on the client side(App gwt + gxt). 

private static Logger log = Logger.getLogger("DateUtils");
.
log.log(Level.INFO, to + " " + from);
return (int) ((to.getTime() - from.getTime()) / MILLIS_IN_DAY);

This code write in chrome console when i  am use two dates:

Thu Nov 06 14:48:34 GMT+300 2014 DateUtils

INFO: Fri Jan 09 00:00:00 GMT+400 2015 Tue Jan 06 00:00:00 GMT+300 2015 


in Russia we have transition 26 october and  now in Moscow, we have always 
timezone GMT +3 (in the past has been the time zone GMT +4).
i am apply to java tzupdater and on server side all it is ok. problem only 
on client side in java.util.Date

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.