mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git

jcambon
07.55.2008 c15ef13192cb53cf8fd0931975a17b1c79441b74
refs
author jcambon <jcambon@localhost>
Monday, April 7, 2008 10:55 +0200
committer jcambon <jcambon@localhost>
Monday, April 7, 2008 10:55 +0200
commitc15ef13192cb53cf8fd0931975a17b1c79441b74
tree eddaaae7914ac1e438569c8fffe51d62dc1c4cdb tree | zip | gz
parent 3d7c5f9f00dd845b1cc8f14d52b48252b10bc375 view | diff
Fix for issue #3089: Configuration Reference - Missing aggregation relations 

To be handle properly, this fix required an enhancement in the Introspection API,
to be able to get the aggregation relations FROM and TO a given managed object.

The following methods have been added to AbstractManagedObjectDefinition class :

getAllAggregationPropertyDefinitions()
getAllReverseAggregationPropertyDefinitions()
getAggregationPropertyDefinition(String name)
getAggregationPropertyDefinitions()
getReverseAggregationPropertyDefinitions()


Then, added the aggregation relations in the the Configuration Reference generated doc,
in sections "Relations From this Component" and "Relations From this component" (today, only the composition relations are listed).

Note that the aggregation relations are not represented in the tree views on the left frame.
Any suggestion to do this is welcome!

2 files modified
368 ■■■■ changed files
opendj-sdk/opends/src/server/org/opends/server/admin/AbstractManagedObjectDefinition.java 183 ●●●●● diff | view | raw | blame | history
opendj-sdk/opends/src/server/org/opends/server/admin/doc/ConfigGuideGeneration.java 185 ●●●●● diff | view | raw | blame | history