112 Chapter 5 { public String hello() throws
112 Chapter 5 { public String hello() throws java.rmi.RemoteException; } The service endpoint interface is required by the Java APIs for XML-based Remote Procedure Calls (JAX-RPC) that works behind the scenes in the container to invoke the bean. The JAX-RPC specification requires that the service endpoint interface follow these rules: The interface must extend java.rmi.Remote either directly or indirectly. All methods must throw java.rmi.RemoteException. The method parameters and return types must be the Java types sup ported by JAX-RPC. Service endpoint interfaces must not include constants (as public final static declarations). The JAX-RPC specification defines a mapping between a set of supported Java types and WSDL/XML types. The Java types directly supported by JAXRPC are the primitive types boolean, byte, double, float, int, long, short, and arrays of these types. In addition, the following non-primitive types are directly supported by JAX-RPC: java.lang.Boolean java.lang.Byte java.lang.Double java.lang.Float java.lang.Integer java.lang.Long java.lang.Short java.lang.String java.math.BigDecimal java.math.BigInteger java.net.URI java.util.Calendar java.util.Date JAX-RPC also provides hooks for customized type mappers that extend the standard type mapping provided by JAX-RPC. In our HelloWorld example, the only data type that is transmitted is java.lang.String, which is mapped to the XML string type without additional effort.
We are dedicated to offering you a reliable, fast, and scalable unlimited web hosting home for your business, and personal web sites.Go and see our shared web hosting services.