On Mon, Feb 6, 2012 at 2:27 PM, Emmanuel Lecharny <[email protected]> wrote: > May be we are looking at the problem from the wrong side. > > All in all, is the user interested into the class used to load the schema ? > What about telling the SchemaManager to load the schema, and telling it to > use a schemaLoader of our choice if needed ? > a very interesting proposal > As of today, we do : > > SchemaLoader loader = new NetworkSchemaLoader( connection ); > > // Load the schemas > SchemaManager schemaManager = new DefaultSchemaManager( loader ); > > What if we do : > > SchemaManager schemaManager = new DefaultSchemaManager( loader ); > schemaManager.loadFromSubentry(); > > ? > > We would have : > > schemaManager.loadFromLdif(); > schemaManager.loadFromJar(); > schemaManager.loadFromSingleLdif(); > schemaManager.loadFromSubentry(); +1 > schemaManager.loadFromAds(); > this will add some unwanted coupling with the network layer, should better be loaded using the below mentioned load( schemaLoader ) method > And for those who would like to use another schemaLoader, we could also have > : > > schemaManager.load( schemaLoader ); > > We then could 'hide' the existing SchemaLoader, ie not expose them to the > public. > From the user POV, that would probably be easier, no ? > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com >
-- Kiran Ayyagari
