Learnings for GWT with JBoss AS 7
I changed my app to run on the newest JBoss (7.0.2) and to use only JavaEE components.
There are a few things that I have learned already:
- JBoss Tools do work only with Maven Projects through m2e.
mvn eclipse:eclipseprojects are not supported and do not work.
- m2e (maven integration for eclipse) does indeed work quite well now. This is new and was not the case a year ago.
- The gwt.xml file may no longer reside in a resource directory, but has to be in a source folder.
- The source folders of the maven gwt plugin and my apt plugin must be inserted manually by the maven resource helper plugin.
- Most Eclipse dependencies are available now in the eclipse market place. This did not work for me with the gwt sdk, which I had to install on the legacy way.
- JBoss comes with a lot of modules activated per default or per trigger (like annotation found). For all modules not activated automatically, an entry in the manifest file like
Dependencies: org.jboss.resteasy.resteasy-cdi,org.jboss.resteasy.resteasy-jackson-provider,org.codehaus.jackson.jackson-jaxrs,org.codehaus.jackson.jackson-mapper-asl,org.codehaus.jackson.jackson-core-aslwill activate them