federation doesn't work with properly functioning tnameserv

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • 1.3.1
    • Affects Version/s: 1.4.0
    • Component/s: core-libs
    • None
    • ladybird
    • sparc
    • solaris_2.6

        In 1.2 & 1.3, when NamingContext.resolve throws NotFound,
        the rest_of_name field is always set to a single element name
        that is the first component of the name that failed. This is
        incorrect. rest_of_name should contain all of the components that
        failed. This problem has been fixed in 1.4.

        For federation, the COS naming provider uses the rest_of_name to determine how
        to continue name resolution into the next naming system (if any).
        Unfortunately, it didn't do it quite right and this error was not
        detected in 1.2 and 1.3 because tnameserv returned the wrong rest_of_name.
        (i.e. the federation tests failed regardless).
        In 1.4, the error in the provider is exposed. A proper functioning provider
        can pass the federation tests when run against a 1.4 tnameserv.

              Assignee:
              Rosanna Lee (Inactive)
              Reporter:
              Rosanna Lee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: