web server - Borland Technical Publications

Web Service providers
Java:RPC provider
This provider assumes that the class serving the web service is in the application
archive (WAR). When a web service request arrives, the RPC provider:
1 Loads the Java class associated with the service.
2 Creates a new instance of the object.
3 Invokes the specified method using reflection.
The parameters are:
■
className: The name of the class that is loaded when a request arrives on this
service.
■
allowedMethods: The methods that are allowed to be invoked on this class. The class
can have more methods than listed here; the methods listed here are available for
remote invocation.
Example:
Note
Java:EJB provider
This provider assumes that the class serving the web service is an EJB.
You can expose a previously deployed stateless session bean as a web service.
When a web service request arrives:
1 The EJB provider looks up the bean name in JNDI initial context.
2 Locates the home class and creates a bean.
3 Invokes the specified method using reflection on the EJB stub.
The actual EJB itself must be deployed to any Partition before a client can access it.
The essential parameters are:
■
beanJndiName: The name of the bean in JNDI.
■
homeInterfaceName: The fully specified class of the home interface. This class must
be present in the WAR.
■
className: The name of the EJB remote interface.
■
allowedMethods: The methods that are allowed to be invoked on this EJB, separated
by spaces. The EJB can have more methods than listed here; the methods listed
here are available for remote invocation.
Example:
76 BES Developer’s Guide