Date: 2004-01-30T08:33:44
Editor: DavanumSrinivas <[EMAIL PROTECTED]>
Wiki: Apache Geronimo Wiki
Page: EnterpriseWebServices
URL: http://wiki.apache.org/geronimo/EnterpriseWebServices
no comment
Change Log:
------------------------------------------------------------------------------
@@ -5,24 +5,24 @@
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.
-1) Our initial design is to use the Remote interface of the EJB to the accsess
the ejb
-(simply put - convert the SOAP request of the webservice to RMI/IIOP request
and the result
-is send back as SOAP by webservice.) We also thought of making the J2EE
container and implementation independent of each other.
+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.
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
+ b) As further explained by the EJB2.1 spec the webservice ejb endpoint
+ i) be a Stateless 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.
+ 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.
- iii) the home interface seem to not needed as client not creating the
webservice
+ iii) the home interface seem to not needed as client not creating the
Web Service
- iv) concerns about mapping of j2ee and ws transaction contexts when we
use remote
+ iv) concerns about mapping of j2ee and Web Service transaction
contexts when we use remote
interface
-we are trying to take a more geronimo based approach. The key idea is to use
geranimo internals to acsess 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 editable ASAP.) We have implemented most of
parts in previous proposal and the code is at http://sf.net/projects/ews/.
+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/.
