Uploaded image for project: 'Directory Client API'
  1. Directory Client API
  2. DIRAPI-253

The AVA class is not handling correctly the values wrt the SchemaManager

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0-M31
    • Fix Version/s: 1.0.0-M32
    • Labels:
      None

      Description

      When we create an Ava, it may be schema aware (or not). In both case, we have to be able to return the user provided value (UPValue) and the normalized value (normValue). For instance, in cn=TEST, the upValue is TEST and the normValue is test.

      Currently, we store those two things in two Value<?> fields, which is really wrong, because :

      • if the Ava is schema aware, one single Value<?> will hold both the upValue and normValue, no matter what
      • if the Ava is not schema aware, there is no way we can make a difference between the upValue and normValue.

      The direct consequence, beside the fact that we are holding one more Value<?> than necessary in the object, is that we can't really propagate easily the schemaManager to the Value<?> instance, if we first create an Ava without schema nad inject the schema later.

        Activity

        Show
        elecharny Emmanuel Lecharny added a comment - Fixed with http://svn.apache.org/viewvc?rev=1708486&view=rev
        Hide
        elecharny Emmanuel Lecharny added a comment -

        It's connected to DIRAPI-254. The fact that we don't have a Value.apply( AttributeType ) method makes it really complicated to create schema aware {{Ava}}s.

        Show
        elecharny Emmanuel Lecharny added a comment - It's connected to DIRAPI-254 . The fact that we don't have a Value.apply( AttributeType ) method makes it really complicated to create schema aware {{Ava}}s.

          People

          • Assignee:
            Unassigned
            Reporter:
            elecharny Emmanuel Lecharny
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development