Vaadin例外は：メソッドがcom.vaadin.shared.ui.ui.UIServerRpc

Question

で0パラメータと認める見つけることができません私は7.7.7にvaadinのバージョンをアップグレードし、私は時々私は次のようなエラーに

java.lang.IllegalStateException: Can't find method acknowledge with 0 parameters in com.vaadin.shared.ui.ui.UIServerRpc 
     at com.vaadin.server.ServerRpcMethodInvocation.findInvocationMethod(ServerRpcMethodInvocation.java:84) ~[vaadin-server-7.7.7.jar:?] 
     at com.vaadin.server.ServerRpcMethodInvocation.<init>(ServerRpcMethodInvocation.java:42) ~[vaadin-server-7.7.7.jar:?] 
     at com.vaadin.server.communication.ServerRpcHandler.parseServerRpcInvocation(ServerRpcHandler.java:590) ~[vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.ServerRpcHandler.parseInvocation(ServerRpcHandler.java:534) ~[vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.ServerRpcHandler.parseInvocations(ServerRpcHandler.java:500) ~[vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:336) ~[vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273) ~[vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.PushHandler$2.run(PushHandler.java:148) ~[vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.PushHandler.callWithUi(PushHandler.java:240) [vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.PushHandler.onMessage(PushHandler.java:494) [vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.PushAtmosphereHandler.onMessage(PushAtmosphereHandler.java:87) [vaadin-server-7.7.7.jar:7.7.7] 
     at com.vaadin.server.communication.PushAtmosphereHandler.onRequest(PushAtmosphereHandler.java:77) [vaadin-server-7.7.7.jar:7.7.7] 
     at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:199) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:107) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:66) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:2075) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.websocket.DefaultWebSocketProcessor.dispatch(DefaultWebSocketProcessor.java:571) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.websocket.DefaultWebSocketProcessor$3.run(DefaultWebSocketProcessor.java:333) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.util.VoidExecutorService.execute(VoidExecutorService.java:101) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.websocket.DefaultWebSocketProcessor.dispatch(DefaultWebSocketProcessor.java:328) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.websocket.DefaultWebSocketProcessor.invokeWebSocketProtocol(DefaultWebSocketProcessor.java:425) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.container.JSR356Endpoint$1.onMessage(JSR356Endpoint.java:214) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.atmosphere.container.JSR356Endpoint$1.onMessage(JSR356Endpoint.java:211) [atmosphere-runtime-2.2.9.vaadin2.jar:2.2.9.vaadin2] 
     at org.apache.tomcat.websocket.WsFrameBase.sendMessageText(WsFrameBase.java:393) [tomcat-websocket.jar:8.0.24] 
     at org.apache.tomcat.websocket.WsFrameBase.processDataText(WsFrameBase.java:494) [tomcat-websocket.jar:8.0.24] 
     at org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:289) [tomcat-websocket.jar:8.0.24] 
     at org.apache.tomcat.websocket.WsFrameBase.processInputBuffer(WsFrameBase.java:130) [tomcat-websocket.jar:8.0.24] 
     at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:60) [tomcat-websocket.jar:8.0.24] 
     at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler$WsReadListener.onDataAvailable(WsHttpUpgradeHandler.java:203) [tomcat-websocket.jar:8.0.24] 
     at org.apache.coyote.http11.upgrade.AbstractServletInputStream.onDataAvailable(AbstractServletInputStream.java:198) [tomcat-coyote.jar:8.0.24] 
     at org.apache.coyote.http11.upgrade.AbstractProcessor.upgradeDispatch(AbstractProcessor.java:96) [tomcat-coyote.jar:8.0.24] 
     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:663) [tomcat-coyote.jar:8.0.24] 
     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1527) [tomcat-coyote.jar:8.0.24] 
     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1484) [tomcat-coyote.jar:8.0.24] 
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_66] 
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_66] 
     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:8.0.24] 
     at java.lang.Thread.run(Thread.java:745) [?:1.8.0_66] 

を取得していますソースをチェックして、7.7.0のUIServerRpcインターフェースで利用可能なメソッドであり、7.7.7にはありません。

@NoLoadingIndicator 
public void acknowledge(); 

これはバダジンのバグですか？または、これは私のコードで何か問題がありますか？

Answer 1

原因は、vaadin-maven-pluginのバージョンを7.7.7にアップグレードすることを忘れていたためです。そのため、以前のバージョンのvaadinでコンパイルされたウィジェットセットは、別のメソッドシグネチャを使用していました。7.7.7

vaadin-maven-pluginのバージョンを7.7.7にアップグレードすると問題が修正されました。