I don't know if this is a good idea since the registries are services - I'd leave it up to dependency injection
to handle populating dependent services like the interceptors. You're also presuming that these registries
will be used only in the code (methods) dealing with request processing. There are other places where they
Also you cannot split up the registries just for a specific partition. Maybe I did not understand properly because
does not make sense. Can you clarify?
On 10/3/07, Alex Karasulu <firstname.lastname@example.org > wrote:
> What registries are you referring to? Schema registries?
> On 10/3/07, Emmanuel Lecharny (JIRA) <email@example.com > wrote:
> > Injecting more information in the opContext structure
> > -----------------------------------------------------
> > Key: DIRSERVER-1081
> > URL:
> > Project: Directory ApacheDS
> > Issue Type: Improvement
> > Affects Versions: 1.5.1
> > Reporter: Emmanuel Lecharny
> > Fix For: 2.0.0
> > As each server operations now use this opContext for every operations, it
> would be useful to inject more information into this context, like access to
> the registries, or other things which are currently stored locally in each
> interceptors during the initialization phaze.
> > It will be more elegant, will allow global modification of the server
> without having to reinit all the interceptors, and could help to define
> specific operation's context for a request (for instance, if we think about
> an operation associated to a specific partition, we could perfectly inject
> the partition associated registries, allowing us to have per-partition
> regristries, instead of one single registries set for all the partition -
> just an idea)
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.