XDoclet module for GWTHaving used Google Web Toolkit to build an application, I found out that I had to write a good portion of code, which might as well be generated automatically. I then decided to mess around with XDoclet a little to see if it was possible to make a new module. It was, and now you can use it too.
Basically, it can generate service interfaces, async services interface, module definitions (.xml.gwt), and a basic web.xml file. Finally, it can create a service factory for creating new Async-objects.
Service interfaces
When creating a remote service, just annotate the class like this:
-
package dk.contix.gwt.service;
-
-
/**
-
* @gwt.interface service="dk.contix.gwt.shared.RemoteService" path="/remoteService"
-
*/
-
public class RemoteServiceImpl implements RemoteService {
-
-
/**
-
* @gwt.serviceMethod
-
*/
-
public String getStuff(String what) {
-
// code here
-
}
-
}
This will create the interface dk.contix.gwt.shared.RemoteService containing all methods which are annotated with @gwt.serviceMethod. It will also generate the async interface in dk.contix.gwt.shared.RemoteServiceAsync
Modules
To generate module definitions (.gwt.xml files), annotate the EntryPoint classes, like this:
-
package dk.contix.gwt.client;
-
-
/**
-
* @gwt.module package="dk.contix.gwt" include="client,shared"
-
*/
-
public class Client implements EntryPint {
-
// code here
-
}
This will generate a file in dk/contix/gwt calles Client.gwt.xml. The file will contain the entry-point declaration, all remote servlets, and additional source paths (those specified in the include parameter).
ServiceFactory
If a service factory is generated, a class with static methods for creating instances of the Async interfaces will be created. The factory class will automatically detect url prefixes (if the application is deployed in another context than ROOT).
Generating the files
Create a build.xml file for Ant, if you don't already have one. Include the following target:
-
<path id="classpath">
-
<pathelement location="src"/>
-
<pathelement location="${build.dir}/classes"/>
-
<fileset dir="lib">
-
<include name="**/*.jar"/>
-
</fileset>
-
</path>
-
-
<target name="generate">
-
<taskdef resource="xdoclet/modules/gwt/doclet.xml" classpathref="classpath"/>
-
-
<gwtdoclet destdir="src">
-
<fileset dir="src">
-
<include name="**/*.java"/>
-
</fileset>
-
-
<interface/>
-
<async/>
-
<module/>
-
<webxml output="web.xml"/>
-
<servicefactory class="dk.contix.gwt.client.ServiceFactory"/>
-
</gwtdoclet>
-
</target>
Finallt, place xdoclet-gwt-module-0.1.jar in lib/ so that it becomes a part of the classpath. xdoclet-*.jar and xjavadoc-*.jar is also required. They can be downloaded from xdoclet.sourceforge.net.
Bootstrapping
When a new remote service is created, there's no interface to implement. I work around this simply by annotating the service implementation, generating the code, and then adding the implements declaration.
RSS feeds available for 
