Date: 2004-01-30T05:19:48 Editor: 220.247.246.55 <> Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices
no comment Change Log: ------------------------------------------------------------------------------ @@ -1,2 +1,36 @@ = Implementation Details of code currently in http://sf.net/projects/ews/ = + + the propsel based for the work so far is in +http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal + +the proposed architecture is a tool that generate the webserive , ejb (ws endpoint) and the +code to bind the webserive and the ejb together. +1) 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. + +2)but due to + a) performance consideration (SOAP->RMI/IIOP->Java) + b) As futher explained by the ejb2.1 spec the webservice ejb endpoint + i) be a Staless session bean + + ii) the remote interface(the interface published) is jaxrpc SEI which extends + javax.rmi.Remote not a ususal Remote interface extends javax.ejb.EJBObject. + + iii) the home interface seem to not needed as client not creating the webservice + iv) concerns about mapping of j2ee and ws transaction contexts when we use remote + interface + +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 have implemented most of parts in privous proposal which is at ews right now. + + + + +
