You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by David Jencks <da...@yahoo.com> on 2007/09/29 22:02:23 UTC

[bigbang] Suggestions on how to proceed

Following Alex's suggestion I've been looking at the  
AuthenticatorConfiguration and have some suggestions as to steps to  
follow.  It looks to me as if there are several layers of  
questionable configuration decisions to rectify and probably doing  
the work systematically will be quicker and less confusing.

So far I see two layers of fixes to do:  the <T> components are  
configured through a <T>Configuration object, and the set of <T? 
Configuration objects is held by the ServerStartupConfiguration  
rather than the component that is actually going to be using the <T>  
components at runtime.

So here's what I'm thinking of...

[0] open a jira indicating which <T> I'm working on :-)

[1] remove the <T>Configuration objects so the <T> components can be  
configured directly.  The set of <T> components will still be held by  
the ServerStartupConfiguration at this stage.

[2] move the <T> components from ServerStartupConfiguration to  
whatever component is actually using the <T> at runtime.

For instance,  the Authenticators are used by the  
AuthenticationService  interceptor at runtime, so in step  
2<Authenticator> I'll move the Set<Authenticator> from  
ServerStartupConfiguration to AuthenticationService.

Looking back I see that I only did steps 0 and 1 for Interceptors so  
I will go back and do step 2 for that also.

Make sense?

thanks
david jencks


Re: [bigbang] Suggestions on how to proceed

Posted by Alex Karasulu <ak...@apache.org>.
Note that there is a subtle difference with some of these operation specific
configuration
beans such as SyncConfiguration, ShutdownConfiguration,
RemovePartitionConfiguration,
and AddPartitionConfiguration.  However they just translate into exposing
operations on
the components.  Thing is after these operations are exposed they need to be
removed in
one shot when removing the JNDI coupling.

Something to think about for the future.  You may have dealt with this
already though since
there might have been some (Add|Remove)InterceptorConfigurations but perhaps
we removed
these a while back - don't remember clearly.

Alex

On 9/29/07, Alex Karasulu <ak...@apache.org> wrote:
>
> Perfect sense.  I like the process and started 0 for the partition config
> bean
> hierarchy which is massive so it will take me a lot of time.  Working it
> tho.
>
> I'll add a jira for this now.
>
> The process is just perfect thanks for defining it so clearly.
> Alex
>
> On 9/29/07, David Jencks <da...@yahoo.com> wrote:
> >
> > Following Alex's suggestion I've been looking at the
> > AuthenticatorConfiguration and have some suggestions as to steps to
> > follow.  It looks to me as if there are several layers of
> > questionable configuration decisions to rectify and probably doing
> > the work systematically will be quicker and less confusing.
> >
> > So far I see two layers of fixes to do:  the <T> components are
> > configured through a <T>Configuration object, and the set of <T?
> > Configuration objects is held by the ServerStartupConfiguration
> > rather than the component that is actually going to be using the <T>
> > components at runtime.
> >
> > So here's what I'm thinking of...
> >
> > [0] open a jira indicating which <T> I'm working on :-)
> >
> > [1] remove the <T>Configuration objects so the <T> components can be
> > configured directly.  The set of <T> components will still be held by
> > the ServerStartupConfiguration at this stage.
> >
> > [2] move the <T> components from ServerStartupConfiguration to
> > whatever component is actually using the <T> at runtime.
> >
> > For instance,  the Authenticators are used by the
> > AuthenticationService  interceptor at runtime, so in step
> > 2<Authenticator> I'll move the Set<Authenticator> from
> > ServerStartupConfiguration to AuthenticationService.
> >
> > Looking back I see that I only did steps 0 and 1 for Interceptors so
> > I will go back and do step 2 for that also.
> >
> > Make sense?
> >
> > thanks
> > david jencks
> >
> >
>

Re: [bigbang] Suggestions on how to proceed

Posted by Alex Karasulu <ak...@apache.org>.
Perfect sense.  I like the process and started 0 for the partition config
bean
hierarchy which is massive so it will take me a lot of time.  Working it
tho.

I'll add a jira for this now.

The process is just perfect thanks for defining it so clearly.
Alex

On 9/29/07, David Jencks <da...@yahoo.com> wrote:
>
> Following Alex's suggestion I've been looking at the
> AuthenticatorConfiguration and have some suggestions as to steps to
> follow.  It looks to me as if there are several layers of
> questionable configuration decisions to rectify and probably doing
> the work systematically will be quicker and less confusing.
>
> So far I see two layers of fixes to do:  the <T> components are
> configured through a <T>Configuration object, and the set of <T?
> Configuration objects is held by the ServerStartupConfiguration
> rather than the component that is actually going to be using the <T>
> components at runtime.
>
> So here's what I'm thinking of...
>
> [0] open a jira indicating which <T> I'm working on :-)
>
> [1] remove the <T>Configuration objects so the <T> components can be
> configured directly.  The set of <T> components will still be held by
> the ServerStartupConfiguration at this stage.
>
> [2] move the <T> components from ServerStartupConfiguration to
> whatever component is actually using the <T> at runtime.
>
> For instance,  the Authenticators are used by the
> AuthenticationService  interceptor at runtime, so in step
> 2<Authenticator> I'll move the Set<Authenticator> from
> ServerStartupConfiguration to AuthenticationService.
>
> Looking back I see that I only did steps 0 and 1 for Interceptors so
> I will go back and do step 2 for that also.
>
> Make sense?
>
> thanks
> david jencks
>
>