Generating and deploying legacy schemas

In order to generate and deploy legacy schemas, you must enable generation of the legacy schemas in your MDM Workbench environment.

1. In your development project, open the mdmgen.properties file and set the property [legacySchemas=true]. This file contains options which change the way the MDM Workbench generates code from the model and this property controls whether it generates the legacy schemas or not.
2. Generate the code for the project so that the schemas are generated. You must do these two steps for every project for which you want to generate legacy schemas. Legacy schemas are generated into the project MDMLegacySchemas. Once the legacy schemas have been generated, you must include them in a CBA so they can be deployed. You can add the bundle to the same CBA that contains your development projects, or you can create a separate CBA.
   Important: It is essential that only one instance of this bundle is deployed to the server. Do not add it to two different CBAs. You must also re-deployed this CBA whenever any of your other module projects change. If all your development projects are deployed in one CBA, you can just add the MDMLegacySchemas project to that CBA.
3. To add the bundle to a CBA, open the COMPOSITEBUNDLE.MF manifest file within the META-INF directory of the CBA project and add MDMLegacySchemas to the list of contained bundles (or to the CompositeBundle-Content entry if you're looking at the source view rather than using the Eclipse editor). Also make sure that the CBA imports the com.dwl.base.xml package and exports the com.dwl.base.xml.XSDFinder service. Note that CBAs containing development project bundles will already do this.
4. Deploy the CBA that contains your legacy schemas. Because the legacy schemas are not deployed in a modular way, you will need to make sure that this bundle is re-deployed whenever any of your other development projects change.