-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
None
-
beta
-
sparc
-
solaris_2.6
Several JNDI service providers use a client-side search utility for performing
searches in cases where the server does not perform the search. For examples,
the LDAP provider uses this utility for support searches on its schema tree;
the NIS provider uses this utility to support searches to supplement its
limited single-map searches; the DSML service provider uses this to search
its content and also to generate a list of entries for formatting into DSML.
The problem is that the enumerator produces a list of entries in which the
parent nodes are always returned after its children. Though most applications
cannot expect any ordering in enumerations, it is more logical to return the
parent node first.
searches in cases where the server does not perform the search. For examples,
the LDAP provider uses this utility for support searches on its schema tree;
the NIS provider uses this utility to support searches to supplement its
limited single-map searches; the DSML service provider uses this to search
its content and also to generate a list of entries for formatting into DSML.
The problem is that the enumerator produces a list of entries in which the
parent nodes are always returned after its children. Though most applications
cannot expect any ordering in enumerations, it is more logical to return the
parent node first.