JAX-RPC - Revision history

Krausebe at 13:29, 9 February 2005

2005-02-09T13:29:49Z

← Older revision		Revision as of 13:29, 9 February 2005
Line 141:		Line 141:
	The beans are exposed through a new interface: the endpoint interface. As presented in the client-side programming model, remote clients can access the methods via SOAP 1.1. The EJB container manages transaction and security.		The beans are exposed through a new interface: the endpoint interface. As presented in the client-side programming model, remote clients can access the methods via SOAP 1.1. The EJB container manages transaction and security.

			[[Image:Server_Side_Model.jpg]]
	[figure]

	=== Endpoint Interface ===		=== Endpoint Interface ===

84.191.141.43: /* Deployment Files */

2005-02-04T10:13:41Z

Deployment Files

← Older revision		Revision as of 10:13, 4 February 2005
Line 186:		Line 186:
	=== Deployment Files ===		=== Deployment Files ===

	~~Four~~ ~~deployment files are needed~~ to expose a stateless session bean as a web service.		In order to expose a stateless session bean as a web service, four deployment files are required:

	* ejb-jar.xml		* ejb-jar.xml

84.191.141.43: /* Endpoint Interface */

2005-02-04T10:08:33Z

Endpoint Interface

← Older revision		Revision as of 10:08, 4 February 2005
Line 180:		Line 180:

	public interface TaxiReservationEndpoint extends java.rmi.Remote {		public interface TaxiReservationEndpoint extends java.rmi.Remote {
	public java.lang.String makeReservation (int ~~cruiseId~~, int ~~cabinId~~, double price)		public java.lang.String makeReservation (int taxiId, int customerId, double price)
	throws java.rmi.RemoteException;		throws java.rmi.RemoteException;
	}		}

84.191.141.43: /* Endpoint Interface */

2005-02-04T10:07:53Z

Endpoint Interface

← Older revision		Revision as of 10:07, 4 February 2005
Line 176:		Line 176:
	</portType>		</portType>
	...		...

			'''Endpoint Interface'''

			public interface TaxiReservationEndpoint extends java.rmi.Remote {
			public java.lang.String makeReservation (int cruiseId, int cabinId, double price)
			throws java.rmi.RemoteException;
			}

	=== Deployment Files ===		=== Deployment Files ===

84.191.141.43: /* Endpoint Interface */

2005-02-04T10:04:51Z

Endpoint Interface

← Older revision		Revision as of 10:04, 4 February 2005
Line 162:		Line 162:
	<message name =„RequestMessage“>		<message name =„RequestMessage“>
	<part name=„taxiId“ type=“xsd:int“ />		<part name=„taxiId“ type=“xsd:int“ />
	<part name=„customerId“ type=“xsd:int“/>		<part name=„customerId“ type=“xsd:int“/>
	<part name=„price“ type=„xsd:double“/>		<part name=„price“ type=„xsd:double“/>
	</message>		</message>
	<message name= „ResponseMessage“>		<message name= „ResponseMessage“>

84.191.141.43: /* Generated Stubs */

2005-02-04T09:48:07Z

Generated Stubs

← Older revision		Revision as of 09:48, 4 February 2005
Line 42:		Line 42:

	In order to express the data types of the XML based definition in the Java programming language JAX-RPC provides a mapping. For instance, xsd:string is mapped to the java.lang.String class. Furthermore, the compiler is also able to map nillable and complex types. Thus, certain Java datatypes such as char can not be mapped.		In order to express the data types of the XML based definition in the Java programming language JAX-RPC provides a mapping. For instance, xsd:string is mapped to the java.lang.String class. Furthermore, the compiler is also able to map nillable and complex types. Thus, certain Java datatypes such as char can not be mapped.

			The following code presents an example of a WSDL document and its corresponding endpoint interface.

	''' WSDL document: '''		''' WSDL document: '''
Line 57:		Line 59:
	<portType name = "TaxiProcessor">		<portType name = "TaxiProcessor">
	<operation name = "book">		<operation name = "book">
	<input message = "reservationRequest"/>		<input message = "tns:reservationRequest"/>
	<output message = "tns:reservationResponse"/>		<output message = "tns:reservationResponse"/>
	</operation>		</operation>

84.191.141.43: /* Endpoint Interface */

2005-02-04T09:45:06Z

Endpoint Interface

@@ Line 143: / Line 143: @@
 === Endpoint Interface ===
-To support exposing a stateless session bean as a Web Service endpoint, the EJB 2.1 specification has added a new interface type to the ejb-jar.xml deployment descriptor. A stateless session bean can now have three interfaces: a remote interface, a local interface for Java clients in the same JVM and a service endpoint interface, which describes the web service.
+To support exposing a stateless session bean as a Web Service endpoint, the EJB 2.1 specification has added a new interface type to the ejb-jar.xml deployment descriptor. A stateless session bean can now have three interfaces: a remote interface, a local interface for Java clients in the same JVM and a service endpoint interface describing the web service.
 The interface itself is generated from the '''<portType>''', '''<message>''' and '''<types>''' pieces of the WSDL document. As already described in the endpoint interface part of the client-side programming model, the JAX-RPC compiler needs to ensure that
@@ Line 150: / Line 150: @@
 * each operation throws the Java.rmi.Remote exception.
-The stateless session bean itself implements the methods defined by the endpoint interface. Furthermore, it can implement the endpoint interface directly because the interface is a direct descendent of java.rmi.Remote.
+The stateless session bean itself implements the methods defined by the endpoint interface. Furthermore, it implements the endpoint interface directly since the latter is an immediate descendent of java.rmi.Remote.
 === Deployment Files ===

84.191.19.66: /* Generated Stubs */

2005-02-04T09:33:50Z

Generated Stubs

← Older revision		Revision as of 09:33, 4 February 2005
Line 22:		Line 22:

	1) A Client operates on a remote interface (the “endpoint interface”) to invoke a remote service		1) A Client operates on a remote interface (the “endpoint interface”) to invoke a remote service
	2) A Stub is generated that handles the method invocation and transforms the RPC call into an XML based protocol, such as SOAP.		2) A Stub is generated that handles the method invocation and transforms the RPC call into an XML based protocol, such as SOAP.
	3) The SOAP message is sent via HTTP (or other transport protocols).		3) The SOAP message is sent via HTTP (or other transport protocols).
	4) The web service processes the request and sends a SOAP Response Message.		4) The web service processes the request and sends a SOAP Response Message.

84.191.141.43: /* Generated Stubs */

2005-02-04T09:32:59Z

Generated Stubs

← Older revision		Revision as of 09:32, 4 February 2005
Line 21:		Line 21:
	The figure above demonstrates the procedure of accessing a web service.		The figure above demonstrates the procedure of accessing a web service.

	1) A Client operates on a remote interface (the “endpoint interface”) to invoke a remote service		1) A Client operates on a remote interface (the “endpoint interface”) to invoke a remote service
	2) A Stub is generated that handles the method invocation and transforms the RPC call into an XML based protocol, such as SOAP.		2) A Stub is generated that handles the method invocation and transforms the RPC call into an XML based protocol, such as SOAP.
	3) The SOAP message is sent via HTTP (or other transport protocols).		3) The SOAP message is sent via HTTP (or other transport protocols).
	4) The web service processes the request and sends a SOAP Response Message.		4) The web service processes the request and sends a SOAP Response Message.
	5) This SOAP message is transformed in either a value or an exception (if SOAP default is declared in the WSDL document)		5) This SOAP message is transformed in either a value or an exception (if SOAP default is declared in the WSDL document)

	As a matter of fact, a developer must not generate or parse SOAP messages. It is the JAX-RPC runtime system that converts the APIs calls and responses to and from SOAP messages.		As a matter of fact, a developer must not generate or parse SOAP messages. It is the JAX-RPC runtime system that converts the APIs calls and responses to and from SOAP messages.

Krausebe: /* Deployment Files */

2005-01-25T20:19:18Z

Deployment Files

← Older revision		Revision as of 20:19, 25 January 2005
Line 156:		Line 156:
	Four deployment files are needed to expose a stateless session bean as a web service.		Four deployment files are needed to expose a stateless session bean as a web service.

			* ejb-jar.xml
	[figure]
			* WSDL file
			* JAX-RPC mapping file
			* webservice.xml

	The '''deployment descriptor''' (ejb-jar.xml file), declares the service endpoint interface. Please note, that the <session-type> elements needs to be set to “stateless” and the optional <transaction-type> (if included) to “Container”.		The '''deployment descriptor''' (ejb-jar.xml file), declares the service endpoint interface. Please note, that the <session-type> elements needs to be set to “stateless” and the optional <transaction-type> (if included) to “Container”.