commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons/discovery/xdocs proposal.xml
Date Wed, 18 Feb 2004 10:00:17 GMT
bayard      2004/02/18 02:00:17

  Added:       discovery/xdocs proposal.xml
  proposal.html converted to xml via script
  Revision  Changes    Path
  1.1                  jakarta-commons/discovery/xdocs/proposal.xml
  Index: proposal.xml
  <title>Proposal for Service Discovery</title>
  <section name="Proposal for Service Discovery Package">
  <subsection name="(0) Rationale">
  <p>The Discovery Component is about discovering, or finding,
  implementations for pluggable interfaces.
  It provides facilities intantiating classes in general,
  and for lifecycle management of singleton (factory) classes.
  Fundamentally, Discovery locates classes that implement a given Java interface.
  The discovery pattern, though not necessarily this package,
  is used in many projects including JAXP (SaxParserFactory and others)
  and commons-logging (LogFactory).
  By extracting this pattern, other projects can (re)use it
  and take advantage of improvements to the pattern as Discovery evolves.
  Discovery improves over previous implementations
  by establishing facilities for working within managed environments.
  These allow configuration and property overrides without appealing
  to the global System properties (which are scoped across an entire JVM).
  <subsection name="(1) Scope of the Package">
  This is not indended to be a replacement to be used strictly by the user, but rather
  a replacement to be used directly by projects.  Use by the user is also reasonable,
  but limited due to 'keeping this simple'.  In particular, there is no configuration
  for this discovery service, it relies soley on usage patterns.
  Given a java.lang.Class parameter 'package.Class' that represents a
  fundamental service as either an interface, an abstract class
  (or even a regular class), find an implementation of that class:
  <li>Look for system property named 'package.Class', the value of which is the
      name of an implementation.</li>
  <li>Look for a 'local' property named 'package.Class'...</li>
  <li>Attempt JDK 1.3+ style discovery</li>
  <li>Attempt to load a default implementation</li>
  In all cases, verify that the discovered implementation <b>implements</b>
  The package should :
  <li>Have an API which should be as simple to use as possible</li>
  <li>Be based on usage patterns, not specific configuration file</li>
  <li>Represent proper discovery &amp; class-loading principles</li>
  <li>Be reasonably portable across JDK levels (1.1.8+?)</li>
  <subsection name="(1.5) Interaction With Other Packages">
  <p><em>Services</em> relies on:
    <li>Java Development Kit (Version 1.1 or later)</li>
    <li>[by design] Nothing Else, particularly anything that would be classified as
a 'service'.</li>
  <subsection name="(2) Required Jakarta-Commons Resources">
  <li>CVS Repository - New directory <code>discovery</code> in the 
  <code>jakarta-commons-sandbox</code> CVS repository.</li>
  <li>Initial Committers - The list is provided below. </li>
  <li>Mailing List - Discussions will take place on the general
  <em></em> mailing list. To help list
  subscribers identify messages of interest, it is suggested that the
  message subject of messages about this component be prefixed with
  <li>Bugzilla - New component "discovery" under the "Commons" product
  category, with appropriate version identifiers as needed.</li>
  <li>Jyve FAQ - New category "discovery" (when available).</li>
  <subsection name="(4) Initial Committers">
  <p>The initial committers on the Service Discovery component shall be:</p>
    <li>Richard A. Sitze</li>
    <li>Costin Manoloche</li>
    <li>Craig R. McClanahan</li>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message