Yeah mainly.

Ideally only your main class deals with configuration parsing and it
constructs all the zk server objects using the public api which is DI
friendly.

For example, I think we should move the main() method out of the
ZooKeeperServer class.

On Fri, Jul 18, 2008 at 1:11 PM, Benjamin Reed <[EMAIL PROTECTED]> wrote:
> Can you be a bit more specific and what kind of injection you are
> talking about? Are you just talking about the server configuration?
>
> thanx
> ben
>
> Hiram Chirino wrote:
>> Hi Guys,
>>
>> First off, great project!  I think ZooKeeper is a fabulous idea.  I
>> can see folks wanting to embedd ZK servers in their products too.  I
>> could see the ActiveMQ project embedding it for several reasons.  And
>> with that in mind,  I think it would be awesome of ZK tried to use
>> more dependency injection (DI) to configure it's objects.  That way
>> and embedding project could directly configure it with java code, or
>> use Spring or Guice etc. etc.
>>
>> If you guys are interested in supporting this use case, I'd be happy
>> to start contributing patches to make that happen.
>>
>>
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

Reply via email to