Proposal for Service Manager Package

(0) Rationale

Some projects (Jakarta-Struts, for example... 8) ) needs for extending by the multiple ways. And each extending is core API modification, which sometimes is not so neccessary for every developer. Service Manager add ability to any framework use pluggable Service modules as config-based extensions.

(1) Scope of the Package

Service Manager Package can be used as some kind of universal bridge from central application to the exteranl modules.

The package should :

• Have an API which should be as simple to use as possible
• Provide ability to plug additional modules without recompilation.
• Use Digester as configuration reader.
• Build 'live' configuration model for pluggable Services with ability to extend Digester rules at process of configuration reading and specify its own configuration inside of Service configuration tag.
• Make ServiceManager's config plugguble into parent application config reader if it is based on Digester.

(1.5) Interaction With Other Packages

Services relies on:

• Java Development Kit (Version 1.3 or later)
• commons-digester
• commons-beanutils
• commons-collections
• commons-logging

(2) Required Jakarta-Commons Resources

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

(4) Initial Committers

The initial committers on the Service Manager component shall be:

• Oleg V Alexeev
• Craig McClanahan