Registering Descriptors

How you add descriptors depends on how you created them. You can create project descriptors in OracleAS TopLink Mapping Workbench and export them to a single descriptor file, and set the sessions.xml file to reference the descriptor file. As a result, OracleAS TopLink can load the descriptors into the session automatically. You can also specify a project class in the sessions.xml file. For all other options, use the add descriptors method to register the descriptors, as Table 4-9, "addDescriptors Options" illustrates.

Table 4-9 addDescriptors Options

Format	Description
`addDescriptors(Project)`	Enables you to manually add additional descriptor to the session in the form of a project
`addDescriptors(Vector)`	Enables you to add a vector of individual descriptor files to the session in the form of a project
addDescriptor(Descriptor)	Enables you to add individual descriptors to the session

Registering Descriptors after Login

You can register descriptors after the session logs in. Doing this enables you to load self-contained subsystems after the session connects. Descriptors that are registered this way are independent of descriptors that are already registered.

To change a descriptor and redeploy it with a minimum of down time, you can also reregister descriptors that are loaded in the session. You must also reregister all related descriptors at the same time, because changes to one descriptor may affect the initialization of other descriptors.