Proposal for Service Discovery Package

(0) Rationale

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).

(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:

• Look for system property named 'package.Class', the value of which is the name of an implementation.
• Look for a 'local' property named 'package.Class'...
• Attempt JDK 1.3+ style discovery
• Attempt to load a default implementation

The package should :

• Have an API which should be as simple to use as possible
• Be based on usage patterns, not specific configuration file
• Represent proper discovery & class-loading principles
• Be reasonably portable across JDK levels (1.1.8+?)

(1.5) Interaction With Other Packages

Services relies on:

• Java Development Kit (Version 1.1 or later)
• [by design] Nothing Else, particularly anything that would be classified as a 'service'.

(2) Required Jakarta-Commons Resources

• CVS Repository - New directory discovery in the jakarta-commons-sandbox CVS repository.
• Initial Committers - The list is provided below.
• Mailing List - Discussions will take place on the general commons-dev@jakarta.apache.org 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 [discovery].
• Bugzilla - New component "discovery" under the "Commons" product category, with appropriate version identifiers as needed.
• Jyve FAQ - New category "discovery" (when available).

(4) Initial Committers

The initial committers on the Service Discovery component shall be:

• Richard A. Sitze
• Costin Manoloche
• Craig R. McClanahan