18.3.4. Illustration

Illustration of the relationship between the configuration files.
The JSF-View in more detail:
  • manager.uiUser.attribute: manages and stores the dynamic properties
    • examples: manager.uiUser.attribute.gender, manager.uiUser.attribute.interests
      <h:inputText id="gender" value="#{manager.uiUser.attribute.gender}" />
  • metadataservice
    • required - references the required attribute from the ui-component example: metadataservice.gender.required
      <h:inputText id="gender" value="#{manager.uiUser.attribute.gender}" required="#{metadataservice.gender.required}"/>
    • values - references the values list from the ui-component example: metadataservice.gender.values
      <h:selectOneMenu id="interests" value="#{manager.uiUser.attribute.interests}">
          <f:selectItems value="#{metadataservice.interests.values}" />
    • validator - references the name of a registered JSF validator example:metadataservice.gender.validator - the first validator of the validator list example: metadataservice.gender.validators[0] - the validator list with an index
      <f:validator validatorId="#{metadataservice.gender.validator}"/>
    • converter - references the name of a registered JSF converter example: metadataservice.gender.converter
      <f:converter converterId="#{metadataservice.gender.converter}"/>
    • readOnly - references the access-mode of profile-config.xml possible usage i.e. in /WEB-INF/jsf/common/profile.xhtml
      <h:inputText value="#{manager.uiUser.attribute.nickname}" disabled="#{metadataservice.nickname.readOnly}" />


The values of the profile-config.xml have a higher priority than the values in the user portlet configuration. That means if the 'usage' is 'mandatory' in profile-config.xml and 'required' is 'false' it will be overwritten by the value from the profile config!