You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lecharny <el...@gmail.com> on 2006/12/05 10:53:02 UTC
A little bit of organization
Hi Alex, hi guys,
What about a little bit box moving ? We are working on the new dynamic
schema, and I just find the actual packages little bit too simple. I would
like to organize it a little bit differently, like :
o.a.d.server.core.schema.meta for the meta schema
o.a.d.server.core.schema.matchingrule for matching rules
o.a.d.server.core.schema.comparator for comparators
o.a.d.server.core.schema.normalizer for normalizers
o.a.d.server.core.schema.syntax for syntax checkers
or something like that. wdyt? May be you have better ideas, I just popped
this out of my head while I was under my shower this mornoing, so it's just
a draft.
Thanks !
--
Cordialement,
Emmanuel Lécharny
Re: A little bit of organization
Posted by Ole Ersoy <ol...@yahoo.com>.
Hey Guys,
Speaking of class loading.
I'm thinking about having the JPackage plugin generate
the class loaders.
So for instance apacheds-server-main would have it's
own classloader that loads all the classes
in the jar that this artifact corresponds to.
Each ApacheDS maven project that has its packaging set
to jar
and contains java files in that jar would have a
corresponding
maven class loader project that is automatically
created by the
JPackage RPM packaging project.
Does that sound ok?
Cheers,
- Ole
--- Alex Karasulu <ak...@apache.org> wrote:
> Emmanuel Lecharny wrote:
> > Alex Karasulu a écrit :
> >
> >>
> >> Hey,
> >>
> >> Yeah I used to have it that way a few years ago
> as a matter of fact.
> >> However there was not much there then so I
> consolidated.
> >>
> >> Perhaps it's time to break things apart again.
> However what's the
> >> motive for the package reorganization?
> >
> > Well, I just started to write some more
> syntaxChecker (as we need some
> > of them for the metaSchema), and as we have
> something like 30 SC to
> > implement (as of RFC 4517), I just think they
> deserve a specific
> > package, because we will also have around 30
> normalizers, and 30
> > comparators, so around 100 java files in the same
> package seems to me a
> > little bit too much.
>
> Sounds like a good reason. Same one that I thought
> but perhaps you had
> other reasons as well. Let's do it.
>
> > However, I also think we must discuss that a
> little bit further, because
> > we might want to allow ADS administrators to add
> their own syntax
> > checkers, which will induce some different
> packaging.
>
> Yeah more than just admins. We want people that can
> manage schema
> (allowed to based on ACI) to be able to do that
> which entails adding
> more of these code components: syntaxCheckers,
> comparators, and normalizers.
>
> So they can use any package name they like. Also
> the way we will
> represent them in the meta-schema and the subscheme
> entries will be
> interesting. Namely we will keep their bytecode in
> the metaschema entry
> and represent these entries as attributes within the
> subschemaSubentry.
>
> This will require some custom class loading which we
> need to discuss.
> First thing first, we need the standard syntax
> checkers, a meta-schema,
> and schema entity description parsers for these
> entities.
>
> Glossary:
>
> *metaschema* => schema to represent schema
>
> *subschemaSubentry* => attribute that points to one
> massive entry
> containing a bunch of attributes that store schema
> entity descriptions
> in attributes
>
> *schema entity description parsers* => basically we
> have attributes in
> the schema subentry like syntaxes, attributeTypes,
> objectClasses,
> matchingRules etc where each value of these
> attributes uses a special
> syntax to describe a schema entity. In the syntaxes
> attribute a syntax
> description is provided. In matchingRules a
> matchingRule description is
> provided.
>
>
> HTH, let me know if there is more that needs
> clarification so other
> understand us.
>
> Regards,
> Alex
>
>
> > begin:vcard
> fn:Alex Karasulu
> n:Karasulu;Alex
> org:Apache Software Foundation;Apache Directory
> adr:;;1005 N. Marsh Wind Way;Ponte Vedra
> ;FL;32082;USA
> email;internet:akarasulu@apache.org
> title:Member, V.P.
> tel;work:(904) 791-2766
> tel;fax:(904) 808-4789
> tel;home:(904) 808-4789
> tel;cell:(904) 315-4901
> note;quoted-printable:AIM: alexokarasulu=0D=0A=
> MSN: aok123@bellsouth.net=0D=0A=
> Yahoo!: alexkarasulu=0D=0A=
> IRC: aok=0D=0A=
> PGP ID: 1024D/4E1370F8 BBCC E8D8 8756 2D51 C3D4
> 014A 3662 F96F 4E13 70F8=0D=0A=
>
> x-mozilla-html:FALSE
> url:http://people.apache.org/~akarasulu
> version:2.1
> end:vcard
>
>
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
Re: A little bit of organization
Posted by Alex Karasulu <ak...@apache.org>.
Emmanuel Lecharny wrote:
> Alex Karasulu a écrit :
>
>>
>> Hey,
>>
>> Yeah I used to have it that way a few years ago as a matter of fact.
>> However there was not much there then so I consolidated.
>>
>> Perhaps it's time to break things apart again. However what's the
>> motive for the package reorganization?
>
> Well, I just started to write some more syntaxChecker (as we need some
> of them for the metaSchema), and as we have something like 30 SC to
> implement (as of RFC 4517), I just think they deserve a specific
> package, because we will also have around 30 normalizers, and 30
> comparators, so around 100 java files in the same package seems to me a
> little bit too much.
Sounds like a good reason. Same one that I thought but perhaps you had
other reasons as well. Let's do it.
> However, I also think we must discuss that a little bit further, because
> we might want to allow ADS administrators to add their own syntax
> checkers, which will induce some different packaging.
Yeah more than just admins. We want people that can manage schema
(allowed to based on ACI) to be able to do that which entails adding
more of these code components: syntaxCheckers, comparators, and normalizers.
So they can use any package name they like. Also the way we will
represent them in the meta-schema and the subscheme entries will be
interesting. Namely we will keep their bytecode in the metaschema entry
and represent these entries as attributes within the subschemaSubentry.
This will require some custom class loading which we need to discuss.
First thing first, we need the standard syntax checkers, a meta-schema,
and schema entity description parsers for these entities.
Glossary:
*metaschema* => schema to represent schema
*subschemaSubentry* => attribute that points to one massive entry
containing a bunch of attributes that store schema entity descriptions
in attributes
*schema entity description parsers* => basically we have attributes in
the schema subentry like syntaxes, attributeTypes, objectClasses,
matchingRules etc where each value of these attributes uses a special
syntax to describe a schema entity. In the syntaxes attribute a syntax
description is provided. In matchingRules a matchingRule description is
provided.
HTH, let me know if there is more that needs clarification so other
understand us.
Regards,
Alex
Re: A little bit of organization
Posted by Emmanuel Lecharny <el...@gmail.com>.
Alex Karasulu a écrit :
>
> Hey,
>
> Yeah I used to have it that way a few years ago as a matter of fact.
> However there was not much there then so I consolidated.
>
> Perhaps it's time to break things apart again. However what's the
> motive for the package reorganization?
Well, I just started to write some more syntaxChecker (as we need some
of them for the metaSchema), and as we have something like 30 SC to
implement (as of RFC 4517), I just think they deserve a specific
package, because we will also have around 30 normalizers, and 30
comparators, so around 100 java files in the same package seems to me a
little bit too much.
However, I also think we must discuss that a little bit further, because
we might want to allow ADS administrators to add their own syntax
checkers, which will induce some different packaging.
Emmanuel
>
> Regards,
> Alex
>
Re: A little bit of organization
Posted by Alex Karasulu <ak...@apache.org>.
Emmanuel Lecharny wrote:
> Hi Alex, hi guys,
>
> What about a little bit box moving ? We are working on the new dynamic
> schema, and I just find the actual packages little bit too simple. I
> would like to organize it a little bit differently, like :
>
> o.a.d.server.core.schema.meta for the meta schema
> o.a.d.server.core.schema.matchingrule for matching rules
> o.a.d.server.core.schema.comparator for comparators
> o.a.d.server.core.schema.normalizer for normalizers
> o.a.d.server.core.schema.syntax for syntax checkers
>
> or something like that. wdyt? May be you have better ideas, I just
> popped this out of my head while I was under my shower this mornoing, so
> it's just a draft.
Hey,
Yeah I used to have it that way a few years ago as a matter of fact.
However there was not much there then so I consolidated.
Perhaps it's time to break things apart again. However what's the
motive for the package reorganization?
Regards,
Alex