(0) rationale
The Web services project currently targets the lower end of the Web Services stack with SOAP, UDDI etc. We need to move up the chain to provide toolkits that support additional functionality as specified for example in the WS-* specifications. A Web Service FX (Functionality Extensions?, Special Effects?) subproject is hereby proposed to accelerate and guide this process.
(1) scope of the subproject
The subproject shall create and maintain implementations for web services specifications written in various languages, including Java and C/C++, intended for use in conjunction with one or more ws.apache.org projects. These components will be designed to be used independently of any larger product or framework, and will pertain directly to web services standards. Each package will be managed in the same manner as a larger Web services product. To further this goal, the subproject shall also host a workplace for Web services committers and a master index of reusable packages related to Web services products.
(1.1) architectural preconditions
Before a constellation of these projects can be fruitfully developed, the Apache-WS community must implement anExtensibilityArchitecture for Axis which allows a common structure and deployment pattern for extensions. See the referenced page for details - essentially we need a way to package and deploy extensions as jar (wsar? xar?) files so that integrating them into Axis is as easy as dropping them into a directory, instead of manually deploying Handlers and rewriting the WSDL processor.
(1.5) interaction with other subprojects
(1.5.1) Axis
See above, section 1.1.
(1.5.2) the sandbox
The subproject will host a CVS repository available to all Apache committers as a workplace for new packages or other projects. Before release to the public, code or documentation developed here must be sponsored by a Web services subproject. The sponsoring subproject(s) will distribute the code or documentation along with the rest of their codebase.
(2) identify the initial source from which the subproject is to be populated
We will start with WS-Security and { { { WS-ReliableMessaging } } }. See the list of proposals.
(3) identify the initial Web services resources to be created
(3.1) mailing list(s)
wsfx
(3.2) CVS repositories
ws-fx
ws-fx-sandbox
(3.3) Bugzilla
program - wsfx
components - Web site
(3.4) Jyve FAQ (when available)
ws-fx-general
ws-fx-sandbox
(4) identify the initial set of committers
Davanum Srinivas (dims@yahoo.com)
Sanjiva Weerawarana (sanjiva@opensource.lk)
Susantha Kumara (susantha@opensource.lk)
Srinath Perera (srinath@opensource.lk)
Glen Daniels (gdaniels@apache.org)
(5) non-committers interested in participating
Questions :
1) What would go in the top-level ws-fx project? Woudldn't ws-fx just be a way of coordinating subprojects?