Yep that's what I thought we should do. First the decoupling and for some time the provider may still reside
in the core until we swap branches because I don't want to have merges cause problems with large scale svn folder
Ok, so I think we can just create this project, and move the JNDI code
for it without any problem. It should keep the server working, but
will help later.
I will give it a try.
Thanks Ersin !
On 10/5/07, Ersin Er <firstname.lastname@example.org > wrote:
> As far as I know that's what we intend to do. The server will itself be
> manageable without the JNDI layer and the JNDI layer will just be an adaptor
> to control the server for those who prefer to interact with JNDI.
> On 10/5/07, Emmanuel Lecharny <email@example.com> wrote:
> > Hu guys,
> > just wondering if it wouldn't be a good idea to have a specific
> > apacheds-jndi sub-project, instead of having this jndi layer inside
> > apacheds-core ?
> > wdyt ?
> > --
> > Regards,
> > Cordialement,
> > Emmanuel Lécharny
> > www.iktek.com
> Ersin Er