Message-ID: <101633496.776064.1386293881429.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_776063_364159578.1386293881429" ------=_Part_776063_364159578.1386293881429 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The architecture guide at the moment is quite weak. It is presumed= that more architecture documentation will be added as more people write mo= dules and extensions to Enunciate. For now, we'll limit the discussio= n of the architecture to a few brief topics.
An Enunciate module is simply a class that implements org.codehaus.enunciate.modul= es.DeploymentModule. If you're writing you're own module, you may= want to start by extending BasicDeploymentModule, or if you want to use Freemarker templates during your generate step (as do most of= the current Enunciate modules), then you may want to extend FreemarkerDepl= oymentModule.
Package your module into a jar, making sure your module class FQN is put= in a file META-INF/services/org.codehaus.enunciate.modules.DeploymentModul= e in the jar (see Sun's d= iscovery process for details). Then, as long as your jar is on th= e classpath when you invoke Enunciate, it should included as part of the en= gine.
If you want to know more, the best place to get a concrete example is by= checking out the Enunc= iate source code, picking a module, and seeing how it's done. You= 'll probably refer to the Javadocs a lot, and fe= el free to post a question on the appropriate mailing = list as well.