When a Java™ API for XML-based RPC (JAX-RPC) Web service application is deployed into WebSphere® Application Server, an instance is created for each application or module. The instance contains deployment information for the Web module or enterprise bean module, including implementation scope, client bindings and deployment descriptor information. There are three levels of scope that can be set: application, session and request.
The Web Services for Java Platform, Enterprise Edition (Java EE) specification states that Web services implementations must be stateless. Therefore, to maintain specification compliance, the scope can remain at the application level because the state relevant to the individual sessions level or the requests level is not supposed to be maintained in the implementation. If you want to deviate from the specification and want to access a different JavaBean instance, because you are looking for information that is located in another JavaBean implementation, the scope settings need to change.
The setting that you configure for the scope determines how frequently a new instance of a service implementation class is created for the Web services ports in a module. Use this task to configure the scope of a Web services port.
You can also configure the scope of a Web services
port with the wsadmin tool. To learn more, see the information on
configuring the scope of a Web services port with the wsadmin tool.
This task applies only to Java API for XML-based RPC (JAX-RPC) Web services.
To change the scope setting in the administrative console:
In this information ...Subtopics
| IBM Redbooks, demos, education, and more(Index) |