webspherewebxml

Generates WebSphere specific deployment descriptors for Web modules. The following files are generated: ibm-web-bnd.xmi and ibm-web-ext.xmi.

NOTE: Since the WebSphere specific deployment descriptors depend on that id's are set in the web.xml file you must genererate it with useIds set to true, e.g. <deploymentdescriptor useIds="true"/>.

This Ant task defines the following attributes (the rest of the attributes in the list below comes from its baseclass):

  • virtualHostName
  • reloadInterval
  • reloadingEnabled
  • defaultErrorPage
  • additionalClassPath
  • fileServingEnabled
  • directoryBrowsingEnabled
  • serveServletsByClassnameEnabled
  • preCompileJSPs
  • autoRequestEncoding
  • autoResponseEncoding
  • autoLoadFilters

NOTE: All attributes except "virtualHostName" are IBM specific WebSphere extensions to the web.xml file and are the same as the attributes that can be found in the IBM WSAD wizard (v5.1.2) for Web Deployment Descriptors (see tab "Extensions" and section "General")

Implementing Class

xdoclet.modules.ibm.websphere.web.WebSphereWebXmlSubTask

Attributes

AttributeDescriptionRequired
virtualHostNameThe virtual host name. "A virtual host is a configuration enabling a single host machine to resemble multiple host machines. This property allows you to bind the application to a virtual host in order to enable execution on that virtual host." No. Default is "default_host"
reloadIntervalA Reload Interval. Every 'reload interval' seconds, the web application's files are checked and reloaded if they have been modified. Requires that reloadingEnabled is set to true. No. Default is "3"
reloadingEnabledSpecifies whether reloading is enabled. No. Default is "true"
defaultErrorPageSpecifies a file name for the default error page. If no other error page is specified in the application, this error page is used. No. Default is ""
additionalClassPathSpecifies an additional class path that will be used to reference resources outside of those specified in the archive. No. Default is ""
fileServingEnabledSpecifies whether file serving is enabled. File serving allows the application to serve static file types, such as HTML and GIF. File serving can be disabled if, for example, the application contains only dynamic components. No. Default is "true"
directoryBrowsingEnabledSpecifies whether directory browsing is enabled. Directory browsing allows the application to browse disk directories. Directory browsing can be disabled if, for example, you want to protect data. No. Default is "true"
serveServletsByClassnameEnabledSpecifies whether a servlet can be served by requesting its class name. Usually, servlets are served only through a URI reference. The class name is the actual name of the servlet on disk. For example, a file named SnoopServlet.java compiles into SnoopServlet.class. (This is the class name.) SnoopServlet.class is normally invoked by specifying snoop in the URI. However, if Serve Servlets by Classname is enabled, the servlet is invoked by specifying SnoopServlet. No. Default is "true"
preCompileJSPsSpecifies wheter JSP pages will be precompiled at deploy time or not. No. Default is "true"
autoRequestEncodingSee IBM WebSphere documentation regarding this attribute. No. Default is "false"
autoResponseEncodingSee IBM WebSphere documentation regarding this attribute. No. Default is "false"
autoLoadFiltersSee IBM WebSphere documentation regarding this attribute. No. Default is "false"
useIdsIf this attribute is set to true, XDoclet will generate id attributes in the XML document. Note that this is only available in some subtasks. No. Default is "false"
xmlencodingThe encoding of the produced xml file. If your XML file uses international characters, you might want to set this to "ISO-8859-1". No, default is "UTF-8"
schemaThe XML Schema to which the generated document should conform. No.
validateXMLIf this is set to true, the generated XML will be validated against its DTD or XML Schema. No, default is false.
acceptInterfacesIndicates whether or not to generate for interfaces. No, default is "true"
acceptAbstractClassesIndicates whether or not to generate for abstract classes. No, default is "true"
packageSubstitutionsSets the PackageSubstitutions attribute of the TemplateSubTask object No.
packageSubstitutionInheritanceSupportedIndicates whether or not package substitution should be inherited No, default is "true"
prefixWithPackageStructureIndicates whether or not to prefix with package structure. No, default is "true"
destinationFileThe destination file name. If a {0} is found it's assumed that a per class output generation is needed, so {0} is substituted with class name; otherwise a single file is generated with the specified name. No, default is determined by this task.
templateFileSets the name of the template file to use for generation No, default is determined by this task.
havingClassTagSets the HavingClassTag attribute of the TemplateSubTask object No.
ofType No.
subTaskNameSets an optional name for the subtask that will be seen in XDoclet's debug messages. No.
destDirSets the directory where the generated file(s) will be written. No.
mergeDirSpecifies the location of the merge directory. This is where XDoclet will look for merge files. No.

Nested Elements

ElementDescription
configParamSpecifies a configuration parameter for the subtask.
ofType
packageSubstitutionSubstitutes the package of the generated files.