Re: [errai-dev] Problems running Errai on AS7 in Eclipse with -Derrai.marshalling.use_static_marshallers=false

From: "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com&gt; Sent: Monday, July 9, 2012 1:19:08 PM Problem - Seems like the client classes are still being deployed at runtime in eclipse. That problem seems to have gone away when I turned off dynamic marshallers. Here is the stack trace from socialpm: [...] 10:00:49,221 ERROR [stderr] (http--0.0.0.0-8080-2) Caused by: java.lang.ClassNotFoundException: com.ocpsoft.socialpm.gwt.client.local.view.events.LogoutEvent from [Module "deployment.socialpm-gwt.war:main" from Service Module Loader] 10:00:49,232 ERROR [stderr] (http--0.0.0.0-8080-2) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) 10:00:49,232 ERROR [stderr] (http--0.0.0.0-8080-2) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) 10:00:49,233 ERROR [stderr] (http--0.0.0.0-8080-2) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) 10:00:49,233 ERROR [stderr] (http--0.0.0.0-8080-2) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) 10:00:49,234 ERROR [stderr] (http--0.0.0.0-8080-2) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) 10:00:49,234 ERROR [stderr] (http--0.0.0.0-8080-2) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) 10:00:49,234 ERROR [stderr] (http--0.0.0.0-8080-2) at java.lang.Class.forName0(Native Method) 10:00:49,235 ERROR [stderr] (http--0.0.0.0-8080-2) at java.lang.Class.forName(Class.java:169) 10:00:49,235 ERROR [stderr] (http--0.0.0.0-8080-2) at org.jboss.errai.cdi.server.events.EventDispatcher.callback(EventDispatcher.java:92) Hmm, from this stack trace it looks like the client classes are not being deployed to the app server (hence the ClassNotFoundException), but for some reason the server-side CDI event dispatcher has received a (client-local) LogoutEvent from the client. I guess that means that either the server-side EventDispatcher has subscribed to that message subject, or the client bus made a bad routing decision in sending that event to the server. Can you list out your subscriptions in the JavaScript console, or use the bus monitor app? That might give us a clue about which scenario we're dealing with. -Jonathan