Date: 2004-06-26T09:35:32 Editor: 203.94.92.227 <> Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices
no comment Change Log: ------------------------------------------------------------------------------ @@ -1,34 +1,30 @@ -= Implementation Details of code currently in http://sf.net/projects/ews/ = - - This page explains the work done so far for the implementation of the (Enterprise WebServices) JSR109 specification. Please not that there is a praposal we forward initially for the project and in EWS project at the sf.net(http://sf.net/projects/ews/. -) we have a working phototype of the implementation based on the initail propoal at http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal += EWS (currently at the apache cvs ws-axis/contib/ews) == +JSR109 defines the Web Services for J2EE architecture. It does not interfere with the J2EE components functionality instead open a new avenue to access them as web services. This is a service architecture that leverages the J2EE component architecture to provide a client and server programming model which is portable and interoperable across application servers, provides a scalable secure environment, and yet is familiar to J2EE developers. -But unfortunatly the initial proposal Based on calling the EJB through the remote interface (for more information please read the URL above) seem to have design issues so we are working on a revised proposal right now. += code == +the code is avalible under the ws-axis/contrib/ews == Architecure == -the proposed architecture is a tool that generate the webserive , ejb (ws endpoint) and the code to bind the webserive and the ejb together. +check the developer guide at the cvs +[http://cvs.apache.org/viewcvs.cgi/*checkout*/ws-axis/contrib/ews/docs/developer-Guide.html?rev=1.1] -== Initial Design == - our initial design is to use the Remote interface of the EJB to the accsess the ejb (simpley put the SOAP requst convert to RMI/IIOP request by the webservice and the result is send back as SOAP by webservice.) We thought of making the J2EE container and implementation independent of each other with that design. -== The problems encountered with the Initial design == - * performance consideration (SOAP->RMI/IIOP->Java) - * As futher explained by the ejb2.1 spec the webservice ejb endpoint should be a be a Staless session bean. The the remote interface(the interface published) is jaxrpc SEI which extends javax.rmi.Remote but not a ususal Remote interface extends javax.ejb.EJBObject. the home interface seem to not needed as client not creating the webservice. We are not supporting these conditions. - * concerns about mapping of j2ee and ws transaction contexts when we use remote interface +== EWS Geronimo integration == +[http://cvs.apache.org/viewcvs.cgi/*checkout*/ws-axis/contrib/ews/dev/Geronimov-ewsIntegration.html] -== Revised Approch == - -we are trying to take a more geranimo based approch. The key Idea is to use geranimo internals to acsess the service implemenation bean and invoke the call on it directly. We would prefer to avoid the SOAP -> RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html (the proposal will bring to wiki and will make editable ASAP.) - -== Security mapping == - -["EnterpriseWebServices/security-mapping"] - -== Transaction mapping == - -["EnterpriseWebServices/transaction-mapping"] +== Contributors == + * Chathura Herath [EMAIL PROTECTED] + * Dasarath Weerathunge [EMAIL PROTECTED] + * Davanum Srinivas [EMAIL PROTECTED] + * Ias [EMAIL PROTECTED] + * Jeremy Lemaire [EMAIL PROTECTED] + * Luis Avila [EMAIL PROTECTED] + * Guillaume Sauthier [EMAIL PROTECTED] + * Ranjit Priyanga [EMAIL PROTECTED] + * Richard Monson-Haefel [EMAIL PROTECTED] + * Srinath Perara [EMAIL PROTECTED]
