Google Web Toolkit: September 2014

Tuesday, September 30, 2014

Re: GWT 2.7 compile time performance for product release builds

Here are some responses from another gwt community thread on the subject of sub 1s refresh times, for for GWT 2.7 and the mgwt kitchen sink example.

https://plus.google.com/111085781306219684730/posts/gb7WEqzr5Kb

"The initial compile is like -draftCompile and if things haven't changed in the mean time you have to pay this time again if you restart the SDM code server (for now). So if you start SDM in a different process (e.g. using Gradle / Maven outside the IDE) you should be fine restarting the IDE."

" The incremental compile process is facilitated by a "MinimalRebuildCache" object that SuperDevMode persists from one compile to the next. At some point we will also persist this cache object to disk and reuse on next process launch, that way even a brand new launch will get some significant performance gains. But there's no timeline on that change. We're still in the process of heavy beta testing for the purpose of flushing out all the bugs from the current implementation."

"production compiles will be about the same as 2.6. This change is an improvement in SuperDevMode compiles and somewhat relies on disabling of optimization and codesplitting, which is not an option for production compiles. So it's an improvement in developer productivity but not an improvement in production compile time."

On Tuesday, September 30, 2014 4:29:34 PM UTC+1, Thanos wrote:

We are seeing a lot about how GWT 2.7 refresh times within Eclipse has improved. Such as this video showing sub 1s refresh times.
https://www.youtube.com/watch?v=qpCSbj36O44&feature=youtu.be

I'm interested to know if there have been any improvements on compilation for product release builds from the command line.

Also are there any improvements within the IDE for the initial first compile, including after IDE restarts.

Mark

--
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+unsubscribe@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: SuperDevMode with -noserver and remote server

Mmm, could it be that my remote server uses HTTPS? I see a javascript warning about this in the console, and just noticed in the release notes something about super dev mode being disabled for security reasons in that scenario and that it didn't work anyway (?). Is there a workaround for that other than not running HTTPS? I know you'll say just run without ssl, but in my case it's not that easy.

On Tuesday, September 30, 2014 4:55:45 PM UTC-6, Thomas Broyer wrote:

On mobile right now so can't look it up but have a look at the release notes, then search in StackOverflow for how to use it. Note this must be enabled before compiling and deploying to your remote server IIRC.

Re: SuperDevMode with -noserver and remote server

On mobile right now so can't look it up but have a look at the release notes, then search in StackOverflow for how to use it. Note this must be enabled before compiling and deploying to your remote server IIRC.

--
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+unsubscribe@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.

Fab Foodie retweeted a photo from Carlost.net on Twitter!

		Carlost.net
		@carlostnet

		#Resurrection S02E01 "Revelation" (Torrent, Firedrive, Sockshare) tmblr.co/ZQxdGy1RwTemj #ResurrectionSeason2 pic.twitter.com/GC0CHBSz8R

		02:23 AM - 29 Sep 14

Retweet

Favorite

View this photo from Carlost.net

Re: SuperDevMode with -noserver and remote server

And what whitelist setting might that be?

On Tuesday, September 30, 2014 3:01:26 PM UTC-6, Michael Joyner wrote:

Just a shot in the dark, but did you enable the whitelist setting in the xml file?

On 09/30/2014 02:26 PM, Rogelio Flores wrote:

I have an app that that has a server with a complex setup and is memory-intensive so we run it on a remote host. Good ol' DevMode runs fine if we run it with -noserver and point to remote host. I just upgraded to latest GWT as it was using an old version, and we want to start using SuperDevMode (SDM). I can run SDM fine if I run the embedded server that comes with GWT and can work on client side code this way, but if I try to run SDM pointing to the remote host (and -noserver), when I click the bookmark "Dev Mode On", I get the popup which shows my module name (although in grayed-out color) but no Compile button appears, so I can't compile/refresh the app. What am I missing to make SDM work on this setup?

--
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+unsubscribe@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.

Re: Logging properties and classes

Not for me, after that I got error in "de/barop/gwt/client/HistoryImplPushState.java", inherited from Errai.

Il giorno martedì 30 settembre 2014 15:41:51 UTC+2, Ümit Seren ha scritto:

Funny I came accross the same issue today (Errai-Bus and GWT-2.7.0-SNAPSHOT).

I filed two issues in the JIRA issue tracker for the Errai project (https://issues.jboss.org/browse/ERRAI-798 and https://issues.jboss.org/browse/ERRAI-799)

You need two workarounds:

1.) Add the logging properties to your gwt.xml file:

<define-property name="gwt.logging.popupHandler" values="ENABLED, DISABLED" />
<define-property name="gwt.logging.firebugHandler" values="ENABLED, DISABLED" />
2.) Creat a com.google.gwt.logging.client package and the FirebugLogHandler class that was removed in 2.7.0

On Tuesday, September 30, 2014 10:58:40 AM UTC+2, Luca wrote:
I tried to recompile a current project upgrading my dependencies from 2.6.1 to 2.7.0-SNAPSHOT, but I had a lot of problem due to missing properties and classes regarding the GWT logging subsystem.

It's a problem of the SNAPSHOT or we need to rework the logging ?

What about external libraries (like Errai) that extensively use logging ?

Thanks.

Re: SuperDevMode with -noserver and remote server

Just a shot in the dark, but did you enable the whitelist setting in the xml file?

On 09/30/2014 02:26 PM, Rogelio Flores wrote:

I have an app that that has a server with a complex setup and is memory-intensive so we run it on a remote host. Good ol' DevMode runs fine if we run it with -noserver and point to remote host. I just upgraded to latest GWT as it was using an old version, and we want to start using SuperDevMode (SDM). I can run SDM fine if I run the embedded server that comes with GWT and can work on client side code this way, but if I try to run SDM pointing to the remote host (and -noserver), when I click the bookmark "Dev Mode On", I get the popup which shows my module name (although in grayed-out color) but no Compile button appears, so I can't compile/refresh the app. What am I missing to make SDM work on this setup?

--
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+unsubscribe@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: SuperDevMode with -noserver and remote server

Thanks, unfortunately this is a project I didn't setup and has an ant build script which would take me some time to convert to maven (something that I'd like to do in near future but want to avoid atm). But isn't the codeserver independent of the server running the compiled app? What would you pass for "ports and hosts" for the setup I'm trying to run? The only parameter I pass to CodeServer is the module name right now and it runs as http://localhost:9876/.

I noticed the reason I don't get the Compile button is that dev_mode_on.js:getCannotCompileError(module_name) returns "The module doesn't have Super Dev Mode enabled". I made sure that I redeployed a new compiled gwt app to the remote-host before running SDM so it should be SDM-enabled. How can I check if it is indeed? I see a "__gwtDevModeHook:myModuleName" string in the "myModuleName.nocache.js" file and it appears to be the same as the one locally.

On Tuesday, September 30, 2014 2:10:41 PM UTC-6, Joseph Lust wrote:

Try using the Maven plugin, should be able to feed it any remote server parameters you need:

mvn gwt:run-codeserver, and just pass the needed ports and hosts.

Joe

Re: SuperDevMode with -noserver and remote server

Try using the Maven plugin, should be able to feed it any remote server parameters you need:

mvn gwt:run-codeserver, and just pass the needed ports and hosts.

Joe

SuperDevMode with -noserver and remote server

I have an app that that has a server with a complex setup and is memory-intensive so we run it on a remote host. Good ol' DevMode runs fine if we run it with -noserver and point to remote host. I just upgraded to latest GWT as it was using an old version, and we want to start using SuperDevMode (SDM). I can run SDM fine if I run the embedded server that comes with GWT and can work on client side code this way, but if I try to run SDM pointing to the remote host (and -noserver), when I click the bookmark "Dev Mode On", I get the popup which shows my module name (although in grayed-out color) but no Compile button appears, so I can't compile/refresh the app. What am I missing to make SDM work on this setup?

Re: XMLHttpRequest: invalid response when loading data from Client Bundle

I understand that moving a SVG file into the defs section into a SVG element is specific to the SVG library used, in this case Snap.svg.

So I opened a thread in a Snap group:

https://groups.google.com/forum/#!topic/snapsvg/8RsMMUaPPCI

But it seems that this requirement cannot be fulfilled with Snap.

I would like to know your opinion: Is this a weakness of this SVG library or can you do it by accessing the DOM directly?

Or would it be better to use another library, e. g. svg.js?

Magnus

Re: Using multiple UiRenderer types in one CellRenderer

On Tue, Sep 30, 2014 at 4:45 PM, Jens <jens.nehlmeier@gmail.com> wrote:

@UiTemplate does not work for UiRenderer?
http://www.gwtproject.org/doc/latest/DevGuideUiBinder.html#Apply_different_xml

Brilliant! I did not know that it existed.

I also noticed that the UiRenderer interface is marked as experimental ... is this still the case what is the future of this with respect to GWT 3.0 ?

No idea, didn't read anything about it. It will probably stay experimental. IMHO the whole cell rendering idea becomes useless as soon as you only support modern browsers (IE 10+) because they are typically faster at DOM operations than calling setInnerHTML with a huge html string. Personally I wouldn't be surprised if cells become deprecated in GWT 4.0 or so.

Oh dear. We are using it very extensively and made quite a lot of customisations on top of the DataGrid/CellTables. But hey, 4.0 is a very long way off!

Thanks for the help.

GWT 2.7 compile time performance for product release builds

We are seeing a lot about how GWT 2.7 refresh times within Eclipse has improved. Such as this video showing sub 1s refresh times.

https://www.youtube.com/watch?v=qpCSbj36O44&feature=youtu.be

I'm interested to know if there have been any improvements on compilation for product release builds from the command line.

Also are there any improvements within the IDE for the initial first compile, including after IDE restarts.

Mark

Re: Using multiple UiRenderer types in one CellRenderer

Am Dienstag, 30. September 2014 15:42:34 UTC+2 schrieb stuckagain:

I'm trying to use multiple UiRenderer types in one CellRenderer. One annoying feature is that you are supposed to use the same base file name for the ui.xml file as the class in which the UiRenderer is defined.

@UiTemplate does not work for UiRenderer?

http://www.gwtproject.org/doc/latest/DevGuideUiBinder.html#Apply_different_xml

I also noticed that the UiRenderer interface is marked as experimental ... is this still the case what is the future of this with respect to GWT 3.0 ?

No idea, didn't read anything about it. It will probably stay experimental. IMHO the whole cell rendering idea becomes useless as soon as you only support modern browsers (IE 10+) because they are typically faster at DOM operations than calling setInnerHTML with a huge html string. Personally I wouldn't be surprised if cells become deprecated in GWT 4.0 or so.

-- J.

Re: How to calculate ages correctly in GWT?

Thanks Thomas. Google Groups ate it.

http://stackoverflow.com/questions/10311754/date-time-library-for-gwt

- Joe

Using multiple UiRenderer types in one CellRenderer

I'm trying to use multiple UiRenderer types in one CellRenderer. One annoying feature is that you are supposed to use the same base file name for the ui.xml file as the class in which the UiRenderer is defined.

In my case I actually want to use multiple UiRenderer interfaces and UiBinder interfaces. Is there some trick to make this possible ? My CellRenderer needs to render differently based on some property of the object it is showing.

I also noticed that the UiRenderer interface is marked as experimental ... is this still the case what is the future of this with respect to GWT 3.0 ?

Re: Logging properties and classes

Funny I came accross the same issue today (Errai-Bus and GWT-2.7.0-SNAPSHOT).

I filed two issues in the JIRA issue tracker for the Errai project (https://issues.jboss.org/browse/ERRAI-798 and https://issues.jboss.org/browse/ERRAI-799)

You need two workarounds:

1.) Add the logging properties to your gwt.xml file:

<define-property name="gwt.logging.popupHandler" values="ENABLED, DISABLED" />

<define-property name="gwt.logging.firebugHandler" values="ENABLED, DISABLED" />

2.) Creat a com.google.gwt.logging.client package and the FirebugLogHandler class that was removed in 2.7.0

On Tuesday, September 30, 2014 10:58:40 AM UTC+2, Luca wrote:

I tried to recompile a current project upgrading my dependencies from 2.6.1 to 2.7.0-SNAPSHOT, but I had a lot of problem due to missing properties and classes regarding the GWT logging subsystem.

It's a problem of the SNAPSHOT or we need to rework the logging ?

What about external libraries (like Errai) that extensively use logging ?

Thanks.

Re: Unable to disable debug IDs

Should anyone else find their way here my colleague pointed me to this:

http://stackoverflow.com/questions/1745315/how-to-create-a-development-debug-and-production-setup

Which explains a little more about the solution suggested below.

On Tuesday, 30 September 2014 11:51:26 UTC+1, Peter Cliff wrote:

I hope this is the right place to ask what I hope is a simple question!

I have a module that is inheriting the debug module and this appears to work - the test debug ID I've added is appearing.

If I add:

<set-property name="gwt.enableDebugId" value="false"/>

the debug IDs disappear.

Now I'd like to be able to control that property from the command line or from Maven during compile (I assume this property takes effect during compile?) so I can turn the IDs on or off for production or otherwise.

(There may be a better way to do that, but I cannot find it - running the app without the debugger on both my PC and our development server I see the debug IDs).

I've tried adding:

-D gwt.enableDebugId=false

to the command line when running mvn gwt:compile but that has no effect.

Adding:

<gwt.enableDebugId>false</gwt.enableDebugId>

to the plugin configuration also does nothing. (I tried enableDebugId without the gwt. too).

Could be I'm going about this all wrong and any advice would be most welcome!

Thank you in advance,

Pete

Re: Unable to disable debug IDs

Thank you Thomas and Joseph - I'll give that go!

Pete

On Tuesday, 30 September 2014 12:39:14 UTC+1, Joseph Lust wrote:

Create another .gwt.xml file that extends your base (testing) .gwt.xml file. Override the property there. Now you're got a testing app you can build for testing and a prod app you can deploy.

-Joe

Re: problem to test the widget TabPanel

Hi All,

I'm facing the same problem, Please share the solution if you have already resolved this issue.

Thanks
Clement Amarnath

On Tuesday, June 18, 2013 8:08:04 PM UTC+5:30, fatimaAngel wrote:

I work on a gwt project, I should create some interfaces using widgets, and everything is good.

here a part of my file .ui.xml

<ui:UiBinder xmlns:ui="urn:ui:com.google.gwt.uibinder"  xmlns:g="urn:import:com.google.gwt.user.client.ui">  <g:TabPanel width="150px" height="130px">  		<g:Tab field="tab1" text="tab1">                       blabla  	        </g:Tab>  </g:TabPanel >

But when i try to test this widget, i have this exception :

com.googlecode.gwt.test.exceptions.GwtTestUiBinderException: Cannot find class 'com.google.gwt.user.client.ui.Tab' declared in file creationInterface.ui.xml

Anybady have idea where is the problem ??

Thanks

Re: How to calculate ages correctly in GWT?

On Tuesday, September 30, 2014 1:47:59 PM UTC+2, Joseph Lust wrote:

You should use Joda Time. GWT does support Joda Time.

Looks like you forgot the link's href, or Google Groups eat it…

Re: How to calculate ages correctly in GWT?

This is not a GWT problem, but basic math. You've already computed the age in milliseconds. Years are quite arbitrary in the West, so you'll need to account for all those leap years, leap seconds, and edge cases.

You should use Joda Time. GWT does support Joda Time.

- Joe

Auto Response

I will be out of office from Sept 30th, 2014 to Oct 9th, 2014. Please contact Mike 2407644639 (mike@globalsyst.com) in my absence. Thanks

Re: Unable to disable debug IDs

Create another .gwt.xml file that extends your base (testing) .gwt.xml file. Override the property there. Now you're got a testing app you can build for testing and a prod app you can deploy.

-Joe

Re: Unable to disable debug IDs

There's no way to override/set GWT binding or configuration properties form the command line; you have to use a gwt.xml file.

But you can simply use a gwt.xml file that <inherits/> your main gwt.xml, rename-to="" the same, and redefines some properties.

See "Renaming modules" in http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html#DevGuideModuleXml

On Tuesday, September 30, 2014 12:51:26 PM UTC+2, Peter Cliff wrote:

<set-property name="gwt.enableDebugId" value="false"/>

the debug IDs disappear.

Now I'd like to be able to control that property from the command line or from Maven during compile (I assume this property takes effect during compile?) so I can turn the IDs on or off for production or otherwise.

(There may be a better way to do that, but I cannot find it - running the app without the debugger on both my PC and our development server I see the debug IDs).

I've tried adding:

-D gwt.enableDebugId=false

to the command line when running mvn gwt:compile but that has no effect.

Adding:

<gwt.enableDebugId>false</gwt.enableDebugId>

to the plugin configuration also does nothing. (I tried enableDebugId without the gwt. too).

Could be I'm going about this all wrong and any advice would be most welcome!

Thank you in advance,

Pete

Re: Logging properties and classes

On Tuesday, September 30, 2014 11:28:12 AM UTC+2, Luca wrote:

Well, not really a bit.......

Being a 2.x I would expect not to have API compatibility broken,

GWT does not follow SemVer.

But I agree we should probably have those 2 properties defined in 2.7 even if they're never used, and remove them in 3.0. Could you file an issue?

I'm not so sure about the classes though…

FYI, the commit that changed it all: https://gwt.googlesource.com/gwt/+/de218e819bd3d0b9818fe40c34999f4fa192e4fc%5E%21/

And if you want a list of all breaking API changes between 2.6 and 2.7: https://gwt.googlesource.com/gwt/+/master/tools/api-checker/config/gwt26_27userApi.conf#147

Exception while adding anchor button to HTMLPanel..

While Adding Anchor button to HTMLPanel i am getting the below error.

lblPanel = new HTMLPanel("sameen");

lblPanel.add(hintButton);

15:28:05.558 [ERROR] [widgetdemo] Uncaught exception escaped

com.google.gwt.event.shared.UmbrellaException: Exception caught: (TypeError) @com.google.gwt.dom.client.Node::removeChild(Lcom/google/gwt/dom/client/Node;)([JavaScript object(50)]): Object doesn't support property or method 'removeChild'

at com.google.gwt.event.shared.HandlerManager.fireEvent(HandlerManager.java:129)

at com.google.gwt.user.client.ui.Widget.fireEvent(Widget.java:129)

at com.google.gwt.event.dom.client.DomEvent.fireNativeEvent(DomEvent.java:116)

at com.google.gwt.user.client.ui.Widget.onBrowserEvent(Widget.java:177)

at com.google.gwt.user.client.ui.ValueBoxBase.onBrowserEvent(ValueBoxBase.java:252)

at com.google.gwt.user.client.DOM.dispatchEventImpl(DOM.java:1351)

at com.google.gwt.user.client.DOM.dispatchEvent(DOM.java:1307)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)

at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)

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:571)

at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:279)

at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)

at com.google.gwt.core.client.impl.Impl.apply(Impl.java)

at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:242)

at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)

at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)

at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)

at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:293)

at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:547)

at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364)

at java.lang.Thread.run(Thread.java:745)

Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError) @com.google.gwt.dom.client.Node::removeChild(Lcom/google/gwt/dom/client/Node;)([JavaScript object(50)]): Object doesn't support property or method 'removeChild'

at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:249)

at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)

at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:571)

at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:279)

at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)

at com.google.gwt.dom.client.Node$.removeChild$(Node.java)

at com.google.gwt.user.client.DOM.removeChild(DOM.java:1023)

at com.google.gwt.user.client.ui.ComplexPanel.remove(ComplexPanel.java:71)

at com.google.gwt.user.client.ui.WidgetCollection$WidgetIterator.remove(WidgetCollection.java:55)

at com.google.gwt.user.client.ui.Panel.clear(Panel.java:78)

at com.jenzabar.jx.ui.widgets.item.LabelBoxField.createHTMLPanel(LabelBoxField.java:192)

at com.jenzabar.jx.ui.widgets.item.LabelBoxField.setRequiredTitle(LabelBoxField.java:111)

at com.jenzabar.jx.ui.widgets.base.FormField.setRequiredErrorOnBlur(FormField.java:288)

at com.jenzabar.jx.ui.widgets.item.TextBoxField$3.onBlur(TextBoxField.java:130)

at com.google.gwt.event.dom.client.BlurEvent.dispatch(BlurEvent.java:56)

at com.google.gwt.event.dom.client.BlurEvent.dispatch(BlurEvent.java:1)

at com.google.gwt.event.shared.GwtEvent.dispatch(GwtEvent.java:1)

at com.google.web.bindery.event.shared.EventBus.dispatchEvent(EventBus.java:40)

at com.google.web.bindery.event.shared.SimpleEventBus.doFire(SimpleEventBus.java:193)

at com.google.web.bindery.event.shared.SimpleEventBus.fireEvent(SimpleEventBus.java:88)

at com.google.gwt.event.shared.HandlerManager.fireEvent(HandlerManager.java:127)