Distinguish between utility classes e.g. LdapNameBuilder and LdapUtils

This one is not a bug report but rather an ux request.

When I started building a method which required me to create new LdapName objects I couldn't tell whether to use LdapNameBuilder or the LdapUtils methods for it. From what I could guess is that I should use the builder class, however, there is nothing that prevents me from using the LdapUtils class which is internally called from the builder anyway.

The JavaDocs for the org.springframework.ldap.support.LdapUtils class has the following opinion:

Generic utility methods for working with LDAP. Mainly for internal use within the framework, but also useful for custom code.

So if this class is for internal use why make it publicy available then? Okay it is usable for custom code, but this custom code could always call the builder too.

Start by reading the public APIs and JavaDocs for LdapNameBuilder and LdapUtils, including how the builder delegates to the utility methods. Determine and document which class should be used for custom LDAP name creation and whether the public utility API needs a clearer distinction or redesign; completion requires an agreed API direction.