Previous | Next | Trail Map | The Basics | Preparations

Names

When you look at the Context(in the API reference documentation) and DirContext(in the API reference documentation) interfaces, you'll notice that there are overloaded forms of each method: one that accepts a String name and one that accepts a Name(in the API reference documentation) . Each pair of these overloaded methods are equivalent in that the Name and String parameters are just different representations of the same name.

Composite Names

The name parameter represents a composite name. This is of significance if you are using a federated naming system. Composite names and federation are explained further in the Beyond the Basics (in the Beyond the Basics trail) trail. For the purposes of this trail, you can just think of and use the name parameter as a name in the target namespace (such as that of your LDAP server).

Preparations: End of Lesson

What's next? Now you can:


Previous | Next | Trail Map | The Basics | Preparations