...
Processing Considerations for Other Operations
Bind
...
Operations
We won't have to implement every operations in the interceptor : some of them are not necessary, like operations which do not modify the entries. For instance, bind() operation is not implemented.
Here is the list of operations defined in the interface, and the list of operations we implement in ReferralService (the missing methods are already implemented in the intermediate abstract class) :
Section |
---|
Column |
---|
| Interface | SchemaService |
---|
add | | addContextPartition | | bind | | compare | | delete | | destroy | |
|
Column |
---|
| Interface | SchemaService |
---|
getMatchedName | | getRootDSE | | getSuffix | | hasEntry | | init | |
|
Column |
---|
| Interface | SchemaService |
---|
isSuffix | | list | | listSuffixes | | lookup | | modify | |
|
Column |
---|
| Interface | SchemaService |
---|
modifyRn | | move | | removeContextPartition | | search | | unbind | |
|
|
Add
AddContextPartition
Compare
Delete
Init
Modify
Modify DN
No Format |
---|
title | RFC 3296 Section 5.6.2 |
---|
|
If the newSuperior is a referral object or is subordinate to a
referral object, the server SHOULD return affectsMultipleDSAs. If
the newRDN already exists but is a referral object, the server SHOULD
return affectsMultipleDSAs instead of entryAlreadyExists.
|
Move
RemoveContextPartition
Search
Conclusions
We will need to alter the ApacheDS JNDI provider, and the LDAP server frontend (MINA LDAP protocol provider) to handle referrals correctly. Here are the changes required for each subsystem.
...