이 콘텐츠는 선택한 언어로 제공되지 않습니다.
23.2. Conversational Web Services
Seam uses a SOAP header element in both SOAP request and response messages to carry the conversation ID beteen the consumer and the service. One example of a web service request containing a conversation ID is:
The above SOAP message contains a
conversationId
element, which contains the conversation ID for the request — in this case, 2
. Because web services can be consumed by a variety of web service clients written in a variety of languages, the developer is responsible for implementing conversation ID propagation between individual web services to be used in a single conversation's scope.
The
conversationId
header element must be qualified with a namespace of http://www.jboss.org/seam/webservice
, or Seam will be unable to read the conversation ID from the request. An example response to the above request message is:
Note that the response message contains the same
conversationId
element as the request.
23.2.1. A Recommended Strategy 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
Since web services must be implemented as either stateless session beans or POJOs, we recommend that conversational web services implement the web service as a facade for a conversational Seam component.
If the web service is written as a stateless session bean, it can be transformed into a Seam component by annotating it with
@Name
. This allows Seam bijection, and other features, to be used in the web service class itself.