Подбор Hi-Fi техники

Корзина пуста...

Умный Дом

A client program creates a new session object when invoking a create method on a session bean home object.

Читать подробнее

Container artifacts

These are the additional classes that the EJB container generates to manage the session bean at runtime and to support the distributed object protocol.

Читать подробнее

Наши работы...

Stateless session beans are particularly well suited for developing Web services. Web services and stateless session beans share significant features of statelessness, and they each have no specific instance identity. Because Web services endpoints that are described using WSDL are stateless—that is, they do not hold state on behalf of clients across client requests—they map nicely into stateless session beans.

Moreover, Web services do not have an instance-specific identity. This means that a request message from a client is not targeted at any particular instance of a Web service. Stateless session beans likewise do not have an instance-specific identity. As a result, each stateless session bean type can be mapped to a WSDL port type. Each operation within the port type maps to a business method of the stateless session bean.

The EJB 2.1 architecture, recently developed as part of the Java Community Process, explains how to develop a Web service using a stateless session bean. This chapter discusses how the EJB 2.1 architecture specifies implementing Web services with stateless session beans.

When developing a Web service using a stateless session bean, the developer should note some differences in the bean's usage. To begin with, the Web service developer does not use the stateless session bean's home interface, as the Web services model does not include the use of the factory pattern implied by the home interface. In addition, the developer models the stateless session bean's business logic interface as a JAX-RPC service endpoint interface.

A developer of a Web services interface needs to follow a few simple rules. The Web services interface extends java.rmi.Remote, and its methods throw the java.rmi.RemoteException exception.