XDoclet Overview News and Status Download/Installation Using XDoclet Best Practices FAQ License Ant Task Reference <ejbdoclet .. /> <webdoclet .. /> <hibernatedoclet .. /> <jdodoclet .. /> <jmxdoclet .. /> <doclet .. /> <documentdoclet .. /> Tag Reference apache (@soap @struts) bea (@weblogic) caucho (@resin) ejb (@ejb @dao) exolab (@castor) hp (@hpas) hibernate (@hibernate) ibm (@websphere) java (@javabean) jboss (@jboss) jdo (@jdo) jmx (@jmx) macromedia (@jrun) mvcsoft (@mvcsoft) mx4j (@mx4j) objectweb (@jonas) orion (@orion) pramati (@pramati) sybase (@easerver) web (@web @jsp) webwork (@webwork) xdoclet (@xdoclet @doc) Feature Documentation Using Value Objects Advanced Maven Plug-in Merge Points Log4J Configuration IDE Integration Migration from EJBDoclet Ant 1.5 Troubleshooting Community Feedback Resources Tools Developer Resources Developer Guide Architecture Branches and Tags CVS Directory Layout XDoclet 2.0 Design Planning Development Reference Javadoc (API) Template Language (*.xdt) Todo List Project Documentation Front Page Project Info Project Reports Development Process | ### webdoclet #### Attributes
Attribute | Description | Required
--- | --- | ---
addedTags | Add some JavaDoc tags (or comments) to the generated classes. A special case @ xdoclet-generated. If this is included, ejbdoclet will not consider the file if it is by error in the fileset of the ejbdoclet task. | No.
destDir | Destination directory for output files | No.
excludedTags | Specify tags that should not be automatically written to output files. The normal behaviour is to include all @ tags from the source file to the output files. This may cause trouble if you use cvs-like tag like $Revision: 1.5 $ that will be overwritten at each build and causes a difference for CVS even if the code himself is not changed. Example: excludedtags="@ version" For excluded tags, ejbdoclet will generate an hardcoded tag. Example: @ version XDOCLET 1.0 | No.
force | Specify if the generation of files should be forced. In normal cases, the timestamp of generated file is checked against the timestamps of the class (and its super classes) we generate from. When this timestamp checking should be bypassed (for example after the installtion of a new xdoclet version) then the user should force the regeneration. The easiest way is to run the Ant build file with a parameter "-Dxdoclet.force=true" and add the option "force=${xdoclet.force}" to the doclet call. | No.
mergeDir | Directory where subtasks will look for files to be merged with generated files. | No, but should be set if you want to use the merge feature.
verbose | Sets the Verbose attribute of the DocletTask object. | No.
#### Nested Elements
Element | Description
--- | ---
configParam | Describe the method
deploymentdescriptor | Generates web.xml deployment descriptor.
fileset | Ant's definition. To define the files to parse.
jbosswebxml | Generates jboss-web.xml deployment descriptor.
jonaswebxml | Generates the web application deployment descriptor for JOnAS.
jrunwebxml | Generates jrun-web.xml deployment descriptor.
jsptaglib | Generates taglib.tld deployment descriptor for JSP taglibs.
packageSubstitution | Substitutes the package of the generated files.
resin-web-xml | Subtask for generation of web.xml with resin extensions.
strutsconfigxml | Generates struts-config.xml deployment descriptor.
strutsvalidationxml | Generates Struts Validator validation.xml deployment descriptor.
subTask |
template | Describe the method
weblogicwebxml | Generates weblogic.xml deployment descriptor for Web apps.
webspherewebxml | This class is responsible for generating the WebSphere specific deployment descriptors.
webworkactiondocs | Generates HTML file containing description of defined WebWork actions.
webworkconfigproperties | Generates views.properties.
xmlTemplate | Describe the method