Hi, I would like to propose a new Jakarta project, named Charon, that should provide a demo implementation of the WSRP Specification (http://www.oasis-open.org/committees/wsrp/).
Please see http://nagoya.apache.org/wiki/apachewiki.cgi?CharonProposal for more details (I've also attached the proposal below). Mit freundlichen Gr��en / Best Regards Peter ___________________________________________________________________ IBM WebSphere Portal Development Boeblingen, Germany Phone: ++49-7031-16-4497 eMail: [EMAIL PROTECTED] (See attached file: charonproposal.txt)
Proposal for Charon ? A Jakarta Sub-project 21, Jan. 2003, Peter Fischer ([EMAIL PROTECTED]) (0) rationale Web Services for Remote Portals (WSRP) are visual, user-facing web services centric components that plug-n-play with portals or other intermediary web applications that aggregate content or applications from different sources. They are designed to enable businesses to provide content or applications in a form that does not require any manual content- or application-specific adaptation by the consuming intermediary applications. As Web Services for Remote Portals include presentation, service providers determine how their content and applications are visualized for end-users and to which degree adaptation, transcoding, translation etc may be allowed. WSRP services can be published into public or corporate service directories (UDDI) where they can easily be found by intermediary applications that want to display their content. Web application deployment vendors can wrap and adapt their middleware for use in WSRP-compliant services. Vendors of intermediary applications can enable their products for consuming Web Services for Remote Portals. Using WSRP, portals can easily integrate content and applications from many internal and external content providers. The portal administrator simply picks the desired services from a list and integrates them, no programmers are required to tie new content and applications into the portal. To accomplish these goals, the WSRP standard defines a web services interface description using WSDL and all the semantics and behavior that web services and consuming applications must comply with in order to be pluggable. The standard allows WSRP services to be implemented in very different ways, e.g. as a Java/J2EE based web services, like JSR168 portlets. The standard enables use of generic adapter code to plug in any WSRP service into intermediary applications rather than requiring specific proxy code. WSRP services are built on standard technologies including SOAP, UDDI, and WSDL. WSRP uses several context elements including user profile, information about the client device, locale and desired markup language passed to them in SOAP requests. A set of operations and contracts are defined that enable WSRP plug-n-play. To enable interoperability between Web Services of different WSRP implementations, IBM initiated the WSRP TC at OASIS. The WSRP Standard will define a set of protocols and conventions for publishing and invoking Web Services between different service providers. As part of the WSRP TC a demo implementation for the Web Service framework will be created. This demo implementation will be based on the Tomcat, Axis, and UDDI sub-projects. (1) scope of the sub-project The purpose of this sub-project is to create and maintain a demo implementation for the WSRP specification as defined in http://oasis-open.org/committees/wsrp. This sub-project will not create a new portal, but only an implementation of a WSRP protocol handler for producer and consumer side plus drivers for both sides. There will be at least a simple driver and a JSR 168 based driver that allows to easily plug in the JSR 168 reference implementation. (2) identify the initial source from which the sub-project is to be populated The WSRP TC has a prototype based on Tomcat, which will be the starting point for the subproject. (3) identify the Jakarta resources to be created (3.1) mailing list(s) charon-user charon-dev (3.2) CVS repositories jakarta-charon (3.3) Bugzilla (3.4) Jyve FAQ (when available) charon-general (4) identify the initial set of committers Peter Fischer ([EMAIL PROTECTED]) David Sean Taylor ([EMAIL PROTECTED]) Stefan Behl ([EMAIL PROTECTED]) (5) identify apache sponsoring individual Sam Ruby ([EMAIL PROTECTED])
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
