Generation

When a nested bean is generated, it will be generated as its own resource collection. One .hrf will be generated that contains the definition of both collections. The collections will be complete and separate for all purposes including access control, versioning, import/export, instance creation, deletion, updates, and publishing. None of these functions are inherited by the child from the parent. The nested beans will not be written to streams by the default implementations of the writeResourcesToStream method on the parent.

Note: The nested beans are not supported as user resources. If the parent is a user resource collection, then the children, by themselves, will be treated as content resource collections and will be content-managed by default. Resources are not affected by the new generation scheme when:

• Resources generated with IBM Content Manager as either a run-time or author-time repository are not affected and will be generated as they have been in previous versions.

• you explicitly override the new generation scheme. If you have resources that depend upon the V4.2 behavior, and want to maintain these resources as-is, edit the .hrf files, and add nestedResourceEnabled=false to the ResourceTable node that corresponds to the secondary table.

 

Back