Web Service Client
Web Service Client
access. If this is the case, either the business interface of the bean must be explicitly designated as
a business interface by being decorated with the @Remote or @Local annotations, or the bean
class must explicitly designate the business interfaces by using the @Remote and @Local
annotations. The same business interface cannot be both a local and remote business interface.
web service created with JAX-WS. (For more information on JAX-WS, see
access a stateless session bean, whether or not the client is written in the Java programming
language. The client doesn't even "know" what technology implements the service: stateless
session bean, JAX-WS, or some other technology. In addition, enterprise beans and web
components can be clients of web services. This flexibility enables you to integrate Java EE
applications with web services.
implementation class. By default, all public methods in the bean class are accessible to web
service clients. The @WebMethod annotation may be used to customize the behavior of web
service methods. If the @WebMethod annotation is used to decorate the bean class's methods,
only those methods decorated with @WebMethod are exposed to web service clients.
following topics apply not only to method parameters but also to method return values.
client and bean operate on different copies of a parameter object. If the client changes the value
of the object, the value of the copy in the bean does not change. This layer of isolation can help
protect the bean if the client accidentally modifies the data.
you should not rely on this side effect of local calls. Perhaps someday you will want to distribute
your components, replacing the local calls with remote ones.