Date: 2004-02-01T07:22:31 Editor: 203.94.92.84 <> Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices
no comment Change Log: ------------------------------------------------------------------------------ @@ -1,28 +1,27 @@ = Implementation Details of code currently in http://sf.net/projects/ews/ = - The original proposal based for the work so far is at http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal + 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 -The proposed architecture consists of a tool that generate the Web Service, EJB's (WS endpoint) and the -runtime code to link the Web Service and the EJB. +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. -1) Our initial design is to use the Remote interface of the EJB to the access the EJB -(simply put - convert the SOAP request to RMI/IIOP request and the result -is sent back as SOAP by Web Service glue code) We also thought of making the J2EE container and implementation independent of each other. +== 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. -2) But due to - a) performance consideration (SOAP->RMI/IIOP->Java) - b) As further explained by the EJB2.1 spec the webservice ejb endpoint - i) be a Stateless session bean +== 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. - ii) the remote interface(the interface published) is JAX-RPC SEI which extends - javax.rmi.Remote not a usual Remote interface that extends javax.ejb.EJBObject. +== The problems encountered with the Initial design == + * performance consideration (SOAP->RMI/IIOP->Java) - iii) the home interface seem to not needed as client not creating the Web Service - - iv) concerns about mapping of j2ee and Web Service transaction contexts when we use remote - interface + * 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 + +== 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.) -we are trying to take a more geronimo based approach. The key idea is to use geronimo internals to access the service implementation 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 edit-able ASAP.) We have implemented most of parts in previous proposal and the code is at http://sf.net/projects/ews/.
