Update Service Data Objects

If we make changes to the schema, we must reload the genmodel and regenerate the SDO. Reloading the genmodel file creates the ecore files used to construct the SDO Java source for your messages.

Before beginning

Updating Service Data Objects requires that a genmodel file and service module has been created. If we already have performed these steps, or have an existing genmodel file and service module, we can skip these prerequisite steps.

• Create a WebSphere Commerce service module.

• Create the genmodel file for the Service Data Objects.

• Generate code from an SDO genmodel file.

Task info

To update the SDOs:

Procedure

1. Start WebSphere Commerce Developer.

2. Right-click the genmodel file and choose Reload.

   

3. Choose Load from an XML schema:

   

4. Browse the workspace to choose the list of schemas to reload from. If all of the changes are internal to existing schemas, then you shouldn't have to do anything at this point; just click Next.

   

5. Select the list of namespaces to include in your genmodel configuration. In this example, select the foundation package. Notice that this schema is dependent on external namespaces, denoted in the bottom tab. Because this is a reload, these dependent schemas are already populated. The first time you load the schema, you would select Browse, and bring in the genmodel file for the dependent schemas.

   At this point you should see the Ecore files for our schemas and all of the dependent schemas. For example:

   

6. Double click the genmodel file to generate the source code for these schemas.

Related concepts
Service Data Objects (SDO)

Related tasks
Creating and updating Service Data Objects (SDO)
Generating code from an SDO genmodel file