The JcaAdapterWizard
extension allows you to add the initial wizard pages. You can add additional wizard pages at any later time. For example, most adapter wizards add their pages after the operation type (inbound/outbound) is selected. If the user changes his mind and selects a different operation type, the wizard pages are removed and new ones added.
Each wizard page collects user input. In addition, an adapter-specific context can be registered to enable sharing information between wizard pages.
When the user selects the Finish button, the framework invokes the buildDataModel()
method on each wizard page in the same order that the pages were displayed. The buildDataModel()
on each page is responsible for copying its screen data to the data model.
The Framework creates artifacts from the data model. Adapters can also register an interface to be invoked before or after the framework's finish processing.
Note:
The Adapter framework handles all WSDL generation. The (old) buildWsdl()
method is still invoked for each wizard page, but most wizard pages should not override this method and leave the WSDL processing to the super class.
The following table describes, and the diagram shows the different classes that makes up the Custom Adapter. A Class Diagram follows.
Table 3-1 Custom Adapter Classes
|
Once you understand the basics, you can proceed to understand the implementation details: