Registering Builders
Once the builders are created, you need to let the Spring infrastructure know about it. Follow the given procedure to register your builder.
 |
To enable deployment of custom builders using the CCD process, a new configuration method for registering builders is provided. The legacy methods for registering custom MVC builders are not supported. A migrator is provided to convert the existing legacy builder registrations to this new method. For more information, see Migrating Builder Registration Configurations.
|
Solution Elements
|
Element
|
Type
|
Description
|
|---|---|---|
|
custom.site.xconf
|
XCONF
|
XCONF file to configure properties in the wt.properties file.
|
|
Custom action definition file
For example: AcmePartClient-actions.xml
|
XML
|
Default XML file for defining actions in the system and triggering the actions using table component ID.
|
|
Table builder class
For example: AcmeTableDataBuilder.java
|
Java
|
Java class to configure table columns and data for the user interface.
|
|
Resource bundle class
For example: CustomAcmeUIResource.java
|
Java
|
The resourceBundle definition to include display names of the new table columns and labels.
|
Modular Structure for Customization
After creating the builder, place the customization artifacts as per the modular structure given below:
<customizationRootDirectory>
├── configurations
│ └── xconf
│ └── custom.site.xconf
└── Acme-UIModule
├── descriptor.xml
└── main
├── resources
│ └── Acme-actions
│ └── AcmePartClient-actions.xml
│ └── config
│ └── mvc
└── src
└── com
└── example
└── newui
├── CustomAcmeUIResource.java
└── mvc
└── builder
└── AcmeTableDataBuilder.java
├── configurations
│ └── xconf
│ └── custom.site.xconf
└── Acme-UIModule
├── descriptor.xml
└── main
├── resources
│ └── Acme-actions
│ └── AcmePartClient-actions.xml
│ └── config
│ └── mvc
└── src
└── com
└── example
└── newui
├── CustomAcmeUIResource.java
└── mvc
└── builder
└── AcmeTableDataBuilder.java
Procedure
1. Create a custom.site.xconf file in the configurations/xconf folder if it has not been already created.
2. Add the custom.mvc.builders.base-packages property in the custom.site.xconf file. Set the value of the property to the name of the base package as shown:
<AddToProperty name="custom.mvc.builders.base-packages" value="com.wizard.mvc.builders"/>
Deploy Customization on Development Environment
For information on the CCD process for deployment, see Deploy Your Customizations on Your Development Environment.
After deployment, a jar file containing the builder is created and the base package is registered in the wt.properties file.
Prepare CCD Package for Promotion
For information on the CCD process for promotion, see Deploying Code and Configuration Package.