Stefan Zoerner wrote:No need to be an architect to see that ! Even me, I can tell how outdated the Javadoc is :/
I am obviously not an expert on this architecture stuff. But I assume, this is outdated.
An interface that bridge underlaying storage of entries and the server API. (Alex will confirm of give a better definition, I think)
The current javadoc of the org.apache.directory.server.core.partition.Partition interface tells usRight.
"An interfaces that bridges between underlying JNDI entries and JNDI Context API."
But JNDI has been removed from the core. Right?
What would be a better short description?
That's ok. OpContext are really used in a mean to limit the number of parameters we have to pass to each specific operation (Add, Delete, etc). It has another major advantage of being extensible, at no cost.
Other question on javadoc:
class AddOperationContext from org.apache.directory.server.core.interceptor.context states the following:
"A Add context used for Interceptors. It contains all the informations needed for the add operation, and used by all the interceptors."
This is still correct, but it is used in Partition as well. Suggestion:
"An Add context used for interceptors and partitions ... "
What do you think?
If it is ok, I'll fix these docs (many other occurrences in other OpContexts ...).