NullPointerException ...gwt.client.MouseEvent (on Vaadin 6.6.1)

General
1

Hey!

After I upgrade my Vaadin from 6.5.3. to 6.6.1, I get a NullPointerException on every button click!

Do you have any solution, why? Bug or feature?

[quote
]java.lang.NullPointerException
at com.vaadin.terminal.gwt.client.MouseEventDetails.deSerialize(MouseEventDetails.java:116)
at com.vaadin.ui.Button.changeVariables(Button.java:198)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariableBurst(AbstractCommunicationManager.java:1297)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariables(AbstractCommunicationManager.java:1217)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleUidlRequest(AbstractCommunicationManager.java:733)
at com.vaadin.terminal.gwt.server.CommunicationManager.handleUidlRequest(CommunicationManager.java:296)
at com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:501)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:591)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:394)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:243)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:188)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

[/quote]

Horst

2

Hi,

when you are using any custom client-side code (including add-ons from the
Directory
), you should always recompile your widgetset when updating your Vaadin version. My guess is that this might be the cause of your NPE .

  • Teemu
3

Hey!
Thanks, but when I recomplie
my Widgetset:

Because why?

Horst

4

You are trying to compile with an old version of GWT. If you are using Vaadin Eclipse plug-in to compile the widgetset, try to switch your project’s Vaadin version to an older version and then back to 6.6.1 to update GWT.

5

Which version of the GWT libraries are you using? Vaadin 6.6.1 requires GWT 2.3.

If you are using the Vaadin Plugin for Eclipse for the compilation, you should first upgrade the plugin to the latest version.

  • Teemu
6

O.K.

I update gwt to 2.3 and than I recompile with eclipse plug in:
i chance in my lib directory the gwt-usr, gwt-dev and the gwt-dev-tooling too:

But the result is the same:

Whats wrong?

Horst

7

Try to add "
?debug
" parameter to the URL to display a debug window (for example
http://demo.vaadin.com/sampler?debug
). In the debug window you can see a line indicating which Vaadin version your widgetset was built with. In this case it should display a line “Widget set is built on version: 6.6.1”

Have you restarted your server after the recompilation?

  • Teemu
8

Hi!

Starting from GWT 2.3, GWT want’s along with the dev and user libs also the validation-api and validation-api-sources libs. Adding that should at least remove some of the problems.

9

Hey !
Thanks to all of you for your support!

But nothing solve my problem, I will get always the same error!

Now I store my resoures for later and delete my widgetsets, and I will try to develop new widgetsets in order it solves my problem!

So I can run my the rest of my application without exceptions, at the moment.

I hobe it will the best workarround at least for now and for me!

Horst

10

I also believe that this is the problem of having old widgetset with newer Vaadin version.

That said - the cause for the NPE was
fixed
 in Vaadin 6.6.2, so try updating to that version.

11

I have done so
thanks