Updated the copyright statement to reflect that Sun owns the full copyright on the project files.
Fix issues 1943 (unable to create je-index), 1996 (exception when creating components with empty names), and 1998 (exception when creating components with blank names). This change allows one-to-many relations to use a property of the referenced component for naming the component. For example, a je-index has an attribute called "index-attribute" which is the attribute type indexed by the index. There is no need for the je-indexes to have a naming attribute since the value of the "index-attribute" property is sufficient. With this change it is possible to specify a "naming property" for one-to-many relations. In the case of je-indexes, the je-backend je-index relation is now defined as follows: <adm:relation name="je-index"> <adm:one-to-many naming-property="index-attribute"/> <adm:profile name="ldap"> <ldap:rdn-sequence> cn=Index </ldap:rdn-sequence> </adm:profile> <adm:profile name="cli"> <cli:relation> <cli:default-property name="index-type" /> </cli:relation> </adm:profile> </adm:relation> Note that the one-to-many element now has a "naming-property" attribute which identifies the je-index property which should be used for naming. Also note that the LDAP profile no longer needs a naming-attribute element, since the naming attribute will be the one associated with the index-attribute property.
Add support for specifying the naming attribute in relations.
Add additional validation to the LDAP profile stylesheet: make sure that object classes, attribute types, and rdn sequences are present where required.
Merge admin framework from config-prototype-branch onto trunk.