java.lang.ArrayIndexOutOfBoundsException: 8
at com.vaadin.terminal.gwt.client.MouseEventDetails.deSerialize(MouseEventDetails.java:124)
at com.vaadin.ui.Table.handleClickEvent(Table.java:2142)
at com.vaadin.ui.Table.changeVariables(Table.java:1963)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariables(AbstractCommunicationManager.java:1094)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleUidlRequest(AbstractCommunicationManager.java:590)
at com.vaadin.terminal.gwt.server.CommunicationManager.handleUidlRequest(CommunicationManager.java:266)
at com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:476)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
etc...
I tried to use the ActionHandler on the table instead, in 6.4.5,but i never succeeded in having the handleAction method called, event with a simple code.
this.tbl.addActionHandler(new Action.Handler() {
@Override
public Action[] getActions(Object target, Object sender) {
return new Action[]{new Action("Test")};
}
@Override
public void handleAction(Action action, Object sender, Object target) {
if ("Test".equals(action.getCaption())){
//---
}
}
});
Just to make sure, check that the widgetset you are using comes from the new Vaadin version - it is easy to forget to update or recompile it when upgrading Vaadin.
At least in the past, I have seen MouseEventDetails serialization errors caused by the wrong widgetset version.
I am getting the same error. I recompiled the widgetset in eclipse. Then i rebuilt my project. As I tried to deploy it, eclipe statet, that my widgetset might need a rebuid so I did it again. Still the error persists…
Please state, what I am missing.
[Edit: The debug messages tell me, that my widgetset has the wrong version. I have updated all Vaadin related plugins in eclipse, still the rebuild seems to produce only an outdated widgetset. Is this documentated anywhere? I am running in circles for about an hour now, just because I updated my vaadin version about a week ago and I have to rebuid widgetsets now, just becaus I want to click on an item in a table, which ist not properly done by the eclipse plugin (or I just do not know, how to to this the proper way). ]
This sounds like a caching problem. Try destroying all relevant cache folders from your application server, and doing a full reload in the browser (shift+reload) and clearing the browser cache as well.
Cleared my cache, removed the portlets from the web-inf dir, removed the temp directory…now it does not even deploy (stuck whent tomcat tells me, copying was done and deploymen will start in a few seconds). I am using liferay as a container. Maybe there is an issue with that? Still did not find any document regarding this. Is there somthing fundermental about updating my vaadin version i fail to understand?
Oh, OK, using Liferay. Not much of an expert on that area, but you might want to look at this add-on, which should help maintain your Liferay installation with Vaadin add-ons:
Vaadin Control Panel for Liferay
Hi,
Did you find a solution ? my initial problem was not on Liferay, but Tomcat. I had this twice. Once because my widgets was outside (another jar) my main app and i didn’t exported it, and the other one was because i have forgetten to update the vaadin.jar in the lib directory of Tomcat and restart it.
Regards