commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: [commons-logging] New services API
Date Wed, 26 Jun 2002 15:08:29 GMT

>> Any objection to checking the 'service' package in under logging and
>> changes to the logger as described?

>I like the concept of abstracting out this logic (mabye we could call it
>"discovery" to avoid name conflict with the "services" package already in
>the sandbox?).  The design pattern is definitely useful and reusable.

Services is a noun, discovery is a verb...  Agree that I've got a
collision.  Also agree that services is overloaded.  I'm going to create
the 'discovery' tree in the sandbox, rename the package to 'org.apache.
commons.service.discovery', and keep my class names as-is.  We can
straighten any remaining concerns out in the sandbox.

I'd also advocate that the existing (more heavy-weight/configurable)
service package be renamed to 'org.apache.commons.service.manager'.  Olag,
what do you think?

>I think making commons-logging depend on it would need a 1.1 release, with
>release notes that prominently highlighted the new dependency.  And that
>would need to wait for a 1.0 release of the discovery thingie.

>You can put the code into the sandbox without a vote (I'll make sure you
>have appropriate karma - every Jakarta committer gets that if they want
>it).  You can add me as a maintainer on your status file.  To get into
>commons proper, though, it'll need a formal vote.  I'd suggest doing the
>grunt work in the sandbox first.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message