XML Data Binding Classes Dialog

Refer to this table when generating a WebApp component implementation.

The XML Data Binding Classes dialog appears if the WebApp component is wired to any reference.

WebApp component supports code generation based on JAXB and XMLBeans. For details, refer to TIBCO ActiveMatrix Java Component Development.

Field Description
Type

The type of the data binding being generated: XMLBeans or JAXB.

If a JAR file already exists for the contract selected in the Contracts list, and you choose a binding type different than the one that exists in the JAR file, or the contract has changed since the JAR file was generated, the Overwrite Existing JAR checkbox will be checked.

Default: XMLBeans.

Contracts Details
Contracts A list of WSDL and schema files for which XML data binding classes will be generated.
JAR Type The type of JAR file being generated: Beans or Interface. (read only)
Source File The path to the source file containing the selected contract. (read only)
JAR File

The path to the JAR file.

Default: When generating a component implementation:

  • Beans
    • For a Plugin Project: projectName/libs/contractFileName.wsdl.jar

    • For a WTP Project: /projectName/WebContent/WEB-INF/lib/contractFileName.wsdl.jar

  • Interface
    • For a Plugin Project: projectName/libs/contractFileName.wsdl_interface.jar
    • For a WTP Project: /projectName/WebContent/WEB-INF/lib/contractFileName.wsdl_interface.jar

Where contractFileName is the name of the file containing the contract selected in the Contracts list and projectName is the name of the project containing the component implementation.

Set JAR Destination Folder Invokes a dialog where you can set the folder to contain generated JAR files:
  • All Generated JARs - All JAR files will be generated in the same folder as the destination of the currently selected JAR.
  • New Generated JARs - Only newly generated JAR files will be generated in the same folder as the destination of the currently selected JAR file.

Setting the JAR folder affects only the JAR files generated by the wizard. It has no effect outside the wizard nor on subsequent wizard runs.

Default: All Generated JARs.

JAR Status The status of the JAR file containing the classes generated for the selected contract:
  • JAR is non-existent and will be generated. - The JAR file does not exist.
  • Different binding type. JAR must be overwritten. - The value of the Type field is different than the type of the data binding classes in the JAR file.
  • JAR exists and will be overwritten. - The JAR file exists and the Overwrite Existing JAR checkbox is checked.
  • JAR exists and will be preserved. - The JAR file exists and the Overwrite Existing JAR checkbox is unchecked.
  • JAR is outdated and will be overwritten. - The selected contract has changed since the JAR file was generated and the Overwrite Existing JAR checkbox is checked, so the JAR file will be generated.
  • JAR is outdated and will be preserved. - The selected contract has changed since the JAR file was generated and the Overwrite Existing JAR checkbox is unchecked, so the JAR file will not be generated.
Overwrite Existing JAR

Enabled only when the JAR file exists. When checked, the JAR file will be regenerated. When unchecked, the existing file will be reused and will not be modified.

Advanced
Use Configuration File

Indicate that the specified data binding configuration file should be used when generating JAR files. When you check the checkbox, the text field is enabled.

Default: Unchecked.