A composite orphan is an MBO child entity within a composite relationship without a
parent entity. For native Object API applications, the upgrade process silently deletes
composite orphans from the server cache. Check all your MBOs to ensure that applications run
properly after the upgrade.
Unwired Platform
version 2.1 ESD #3
no longer allows composite orphans. Depending on the system
configuration, the upgrade may physically delete the orphans, or may only logically
delete them, with physical deletion occurring during a subsequent cache purge process.
Either way, applications that use MBOs with composite orphans may not behave the same
after migration. To avoid problems with existing applications:
- Look for existing MBOs that generate composite orphans. Examine
each MBO in Unwired WorkSpace, looking for any instance in which the application
loads child entities before the related parent entity.
- For any MBOs you find that generate composite orphans, change the
data model in the MBO so that the application always loads parent entities
before the related child entities. See the "Composite relationship behavior" row
in Relationship Guidelines and Restrictions in Sybase Unwired WorkSpace - Mobile Business Object
Development.
- Test any changes you make to ensure that the application still
behaves as expected.
- After you are satisfied that you have eliminated composite
orphans from your MBOs, proceed with the upgrade to Unwired Platform version 2.1
ESD #3.