-
1. Re: Errai in GWT built-in development mode
csa Jul 4, 2012 9:49 AM (in response to throwable)Hi,
This error indicates that Errai didn't find your @Remote interface(s) when scanning the classes. Do you have an ErraiApp.properties on the classpath? It's required for classpath scanning.
Cheers,
Christian
-
2. Re: Errai in GWT built-in development mode
throwable Jul 4, 2012 10:05 AM (in response to csa)Yes, I have ErraiApp.properties in WEB-INF/classes (but it is empty). Also I saw that this interface is present in the generated file .errai/BootstrapperImpl.java.
Salu2,
Antón
-
3. Re: Errai in GWT built-in development mode
csa Jul 4, 2012 10:13 AM (in response to throwable)Well there should be an .errai/RpcProxyLoaderImpl.java which registers the proxy providers for your @Remote interfaces. You could try moving you ErraiApp.properties to the root of your source folder.
-
4. Re: Errai in GWT built-in development mode
throwable Jul 4, 2012 10:28 AM (in response to csa)I did a complete project clean and recompile. The error have gone. But server RPC bean still does not receive messages. It is not initialized by container.
Salu2,
Antón
-
5. Re: Errai in GWT built-in development mode
csa Jul 4, 2012 10:41 AM (in response to throwable)1 of 1 people found this helpfulOK since you're using Errai CDI you need to make sure to have a beans.xml on the classpath and to specify the "-server org.jboss.errai.cdi.server.gwt.JettyLauncher" parameter when starting Development Mode. Also make sure you have a jetty-env.xml and the corresponding setttings in your web.xml. This is necessary to make CDI and the BeanManager available in Jetty.
Here's an example of these settings from one of our demos: