|This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14/|
On October 27th, 2010, 4:38 a.m., Kiran Ayyagari wrote:I would suggest that we confine the usage of beans to config reader only(even if they can be accessed publicly), cause we need to copy the property values from bean to the corresponding real instance (e.x DirectoryServiceBean -> DirectoryService) and this is better to it in the reader, so we don't need this copying anywhere else to setup a service (one particular area I see is in embedded mode, currently in embedded server we are not able to use external config, but with the new single file LDIF based config it is now possible and setting up a server gets easier too from a user's pov)
On October 27th, 2010, 4:52 a.m., Emmanuel Lécharny wrote:I'm not sure this is a good idea : - if the configBean does the Bean -> real object conversion, then the configBean will have to be aware of the real object. In any case, there is a tight relation between config and entities, and it has to be expressed in either place. - As configBean can be used to store partial results (it contains AdsBaseBeans), you have no way to know which kind of objects you'll get from it : ot can stores AdirectoryService beans (and more than one), Servers, etc. - if the service init needs to read the configBean and search for the exact Bean it has to use, then that mean the service has to know where in the config hierarchy will be stored the Bean. Not very convenient, IMO - also the reader reads, it does not instantiate. In Studio, we don't care instantiating anything, so there is no reason to have this part done in the reader. I created a ConfigCreator for this purpose, btw
On October 27th, 2010, 5:20 a.m., Kiran Ayyagari wrote:Agree with you, the main thing I want to see is to have a single plave where this bean -> real service object conversion/mapping/creation happens. So instead of we changing the startLdap() method to startLdap( directoryServiceBean.getLdapServerBean(), directoryService ); we need a config handler/creator to do this and give us the DirectoryService which we can use directly to start. Am I making sense?
On October 27th, 2010, 5:37 a.m., Emmanuel Lécharny wrote:ATM, the ConfigCreator class is doing the conversion. We can do : startLdap( directoryServiceBean, directoryService ) that would be probably better. If we go any further, another approach would be to nae all the beans, and use PicoContainer : startLdap( container, directoryService ) where inside the startLdap we would do : LdapServerBean ldapServerBean (LdapServerBean)container.get( "ldapServer" ); but this is not where we want to go, I guess...
On October 27th, 2010, 5:43 a.m., Kiran Ayyagari wrote:>> We can do : startLdap( directoryServiceBean, directoryService ) IMHO I want this to be done in the config creator, i.e. like startLdap ( configCreator.createDS(directoryServiceBean) ); so if I want to embed the DS I can use config reader and creator and just start the DS like DirectoryService ds = configCreator.createDS(directoryServiceBean); ds.startup(); I need not copy the code from startLdap( directoryServiceBean, directoryService ) to create the DS and then start >> but this is not where we want to go, I guess... definitely NOT :)
On October 27th, 2010, 6 a.m., akarasulu wrote:+1 on ds.startup() after configCreator.createDS(directoryServiceBean) this makes for a cleaner API.
ok, so what about creating everything in the bean builder, and pass the result to the start methods ? But again, we would like to write : startLdap( ldapInstance, dsInstance ), no ? And how do we get the ldapInstance, btw? configBuilder.getLdapInstance() ? This won't be different from what we currently have...
On October 27th, 2010, 4:24 a.m., Emmanuel Lécharny wrote:
Review request for directory.
By Emmanuel Lécharny.
Updated 2010-10-27 04:24:41