ClassNotFoundException: com.smartgwt.client.util.LogicalDate

[bnagwt]

Hi, we have a compatibility problem after updating nightly build Sun Oct 27 11:20:00 GMT+100 2013 or later EX.:

An IncompatibleRemoteServiceException was thrown while processing this call. com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: org.eclipse.virgo.kernel.osgi.framework.ExtendedClassNotFoundException: com.smartgwt.client.util.LogicalDate in KernelBundleClassLoader: [bundle=…]
…
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserialize(ServerSerializationStreamReader.java:609)
... 33 common frames omitted
Caused by: java.lang.ClassNotFoundException: com.smartgwt.client.util.LogicalDate
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at org.eclipse.virgo.kernel.userregion.internal.equinox.KernelBundleClassLoader.loadClass(KernelBundleClassLoader.java:135)
... 37 common frames omitted

Is there any other component (other than SmartGWT) we need to update for solving this problem?

Tested nightly builds:
OK SmartGWT Version: 4.1d BuildDate: Sun Oct 20 09:59:00 GMT+200 2013
EX. SmartGWT Version: 4.1d BuildDate: Sun Oct 27 11:20:00 GMT+100 2013
EX. SmartGWT Version: 4.1d BuildDate: Tue Nov 12 14:55:00 GMT+100 2013
EX. SmartGWT Version: 4.1d BuildDate: Sat Nov 16 12:38:00 GMT+100 2013
EX. SmartGWT Version: 4.1d BuildDate: Sun Nov 17 11:15:00 GMT+100 2013

Regards Béla

[Isomorphic]

There's no difference between those builds that could create an exception like this, but it would result from not having smartgwt.jar on your server-side classpath or by having a stale smartgwt.jar on your server-side classpath that doesn't match the version that is used in your GWT compile.

The second problem (mismatched smartgwt.jar) would perfectly explain why one build works and the others don't.

For completeness, you only need smartgwt.jar on your server-side classpath if you are using GWT-RPC, and we strongly advise against using GWT-RPC.

[bnagwt]

Your recommended solution to eliminate GWT-RPC is under construction… Yes, it was mismatched smartgwt.jar, thank you!