1、 Access to Additional Content for ECMA-366 3rdEdition, Dated: December 2011 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyri
2、ght holder of this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. ECMA-366 Extra Files Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer 2) “Notification WSDL” that specifies
3、 the interface the Service Requester shall implement in order to receive the event in a particular format using Annex A and the Option in Annex B. 5.1 Provider WSDL Ecma International 2011 34 Ecma International 20115.2 Notification WSDL 6 SOAP Binding This Clause specifies the binding templates of t
4、he abstract WSDL definitions in Clause 5 with SOAP Messages without a specific transport protocol. Any SOAP binding to transport shall contain elements and attributes in this binding template. Ecma International 2011 56.1 SOAP Binding for Provider WSDL 6 Ecma International 20116.2 SOAP Binding for N
5、otification WSDL 6.3 SOAP Binding of sessionID The aps:sessionID element shall be included as a direct child element of the SOAP header for each application SOAP message, such as event notification message, exchanged over the application session. The recipient (Service Provider or Requester) of the
6、application message shall verify that the sessionID is valid; otherwise it shall ignore the message or send a fault. 6.4 SOAP Fault Messages The negative responses from Service Providers shall be bound to the SOAP 1.1 fault properties: faultcode, faultstring and detail, using the following template.
7、 faultcode faultstring detail The contents of fault properties are defined by the following table for each type of negative response. Table 1 Fault names and properties for WS-Session services Fault Name StartFault faultcode ECMA-354 defined standard error names: invalidApplicationInfo, requestedPro
8、tocolVersionNotSupported, serverResourcesBusy, maxNumberSessions, or application error name. faultstring For ECMA-354 standard errors, it is the Description of corresponding error in Table 4-3 of ECMA-354. Additonal text can be provided to elaborate the error message, for example, the maximal sessio
9、n number allowed by the service provider. For application errors, a proper English description shall be provided. detail Element aps:StartApplicationSessionNegResponse. Fault Name StopFault faultcode ECMA-354 defined standard error names: invalidSessionID, or application error name. faultstring For
10、ECMA-354 standard errors, it is the Description of corresponding error in Table 4-6 of ECMA-354. Additonal text can be provided to elaborate the error message, for example, the valid session ID format allowed by the service provider. For application errors, a proper English description shall be prov
11、ided. detail Element aps:StopApplicationSessionNegResponse. Fault Name ResetFault faultcode ECMA-354 defined standard error names: invalidSessionID, serverCannotResetSessionDuration, or application error name. faultstring For ECMA-354 standard errors, it is the Description of corresponding error in
12、Table 4-9 of ECMA-354. Additonal text can be provided to elaborate the error message, for example, the duration allowed by the service provider. For application errors, a proper English description shall be provided. detail Element aps:ResetApplicationSessionTimerNegResponse. 7 Event Subscription an
13、d Notification A Service Providers endpoint of the session is an event source that generates the ApplicationSessionTerminated event notification. That session may also contain other event sources, e.g. CSTA monitors, which generate event notifications within the session. Ecma International 2011 7The
14、 Service Requester shall subscribe to a particular session in a Service Provider to receive event notifications from the session and its contained event sources. The Service Requester shall use the event subscription mechanism of the Service Provider as defined in Annex A and may optionally use the
15、mechanism specified in Annex B if the Service Provider supports it. The Service Requester shall subscribe to a session immediately after receiving the positive response of the StartApplicationSession operation. To associate an event sink endpoint with a session, the event subscription message shall
16、include the unique aps:sessionID obtained from the StartApplicationSession operation (see Clause 6). The Service Provider shall only send notifications for events from a session and its contained event sources to each of the valid event sink endpoints associated with that session. Any subscription t
17、o an invalid session shall result in a SOAP fault message as defined in Annex A and B. When a session terminates, any subscription associated with the session is deemed invalid. 8 Ecma International 2011Annex A (normative) Event Subscription Using WS-Eventing A.1 General The Service Requester and Pr
18、ovider shall conform to WS-Eventing and support the wse:NotifyTo element of WS-Eventing. For wrapped format event delivery, the Service Provider shall implement the SOAP 1.1 binding to the WSDL for Standard Wrapped Delivery specified in Annex D of WS-Eventing. For unwrapped format event delivery, th
19、e Service Provider shall implement the SOAP 1.1 binding to the Notification WSDL specified in Clause 5 of this Standard according to section A.2 of WS-Eventing. The Service Requester shall subscribe to a session (see Clause 7) for either wrapped or unwrapped event delivery format and implement the W
20、SDL and SOAP binding 1.1 required by the Service Provider for the selected format. All notifications from event sources within a session shall include sessionID as specified in Clause 6. A.2 Subscription Fault If the aps:sessionID sessionID in the event subscription request is invalid, the Service P
21、rovider shall return a SOAP 1.1 fault message with these properties: faultcode=”UnknownEventSource” faultstring=”The session sessionID is invalid” detail=invalidSessionID:sessionID Ecma International 2011 910 Ecma International 2011Annex B (normative) Subscription Using WS-BaseNotification Option B.
22、1 General The Service Requester and Provider shall conform to WS-BaseNotification. They shall support the push-style of WS-BaseNotification to deliver the event notifications. The Service Provider shall implement the wsnt:Subscribe operation defined in the NotificationProducer portType of WS-BaseNot
23、ification WSDL and may implement other operations, such as wsnt:Unsubscribe, defined in the SubscriptionManager portType WS-BaseNotification 1.3. For Wrapped Delivery mode, the Service Requesters shall implement SOAP 1.1 binding to the Notification Consumer Interface specified in Section 3 and Apped
24、ix C of WS-BaseNotification. For unwrapped mode (a.k.a. raw in WS-BaseNotification), the Service Provider shall implement the SOAP 1.1 binding to the Notification WSDL specified in Clause 5 of this Standard according to Section 3 of WS-BaseNotification. The Service Requester shall subscribe to a ses
25、sion (see Clause 7) for either wrapped or unwrapped event notification form and implement the WSDL and SOAP 1.1 binding required by the Service Provider for the selected format. All notifications from event sources within a session shall include sessionID as specified in Clause 6. B.2 Subscription F
26、ault If the aps:sessionID sessionID in the request is invalid, the Service Provider shall return a SOAP 1.1 fault message with these properties: faultcode=”wsrf-rw:ResourceUnknownFault” faultstring=”The session sessionID is invalid” detail=invalidSessionID:sessionID Ecma International 2011 1112 Ecma
27、 International 2011Annex C (normative) Asynchronous Response to Subscription Request Option The Service Provider and Requester shall follow WS-Addressing WS-Addressing 1.0 to annotate and correlate event subscription messages for asynchronous message exchange. If the Service Provider only supports s
28、ynchronous response, it shall return a SOAP fault message with faultcode set to wsa:OnlyAnonymousAddressSupported WS-Addressing 1.0 SOAP Binding. An asynchronous event subscription SOAP message template, applicable to both WS-Eventing and WS-BaseNotification, is shown below. xs:anyURI xs:string mess
29、age_id reply_address xs:anyURI xs:any* The template for the reply message (response or fault) is shown below. reply_address message_id xs:anyURI xs:any* Ecma International 2011 1314 Ecma International 2011Annex D (informative) Example WS-Session WSDL binding with SOAP/HTTP D.1 Service Provider WSDL
30、with SOAP/HTTP Binding This Annex provides a more specific and complete binding of the SOAP binding specified in 6.1 by adding the HTTP transport and Service Element. Ecma International 2011 1516 Ecma International 2011D.2 Notification WSDL with SOAP/HTTP Binding This Annex provides a more specific
31、and complete binding of the SOAP binding specified in 6.2 by adding the HTTP transport. Ecma International 2011 1718 Ecma International 2011Annex E (informative) SOAP XML Templates for ECMA-354 Messages E.1 StartApplicationSession request message template Ecma International 2011 19E.1.1 StartApplica
32、tionSession Positive response message template aps:StartApplicationSession aps:StartApplicationSessionPosResponse E.1.2 StartApplicationSession negative response message template An example of negative response due to maximum session limit. maxNumberSessions the server cannot create an application s
33、ession because it has reached the maximum number of allowed application sessions maxNumberSessions E.2 StopApplicationSession request message template 20 Ecma International 2011E.2.1 StopApplicationSession positive response message template aps:StopApplicationSession aps:StopApplicationSessionPosRes
34、ponse E.2.2 StopApplicationSession negative response message template An example negative response due to invalid session reference. invalidSessionID the sessionID is not valid or known by the server invalidSessionID E.3 ResetApplicationSessionTimer request message template Ecma International 2011 2
35、1E.3.1 ResetApplicationSessionTimer positive response message template aps:ResetApplicationSessionTimer aps:ResetApplicationSessionTimerPosResponse E.3.2 Reset Application Session Timer negative response message template An example negative response due to invalid session reference. invalidSessionID
36、 the sessionID is not valid or known by the server invalidSessionID E.4 ApplicationSessionTerminated E.4.1 Template of ApplicationSessionTerminated event notification for unwrapped event sink which applies to both WS-Eventing and WS-BaseNotification options E.4.2 Template of ApplicationSessionTermin
37、ated event notification to wrapped event sink of WS-Eventing http:/www.ecma-international.org/standards/ecma-366/ws-session/ed3/ApplicationSessionSinkPortType/ApplicationSessionTerminated xs:any* aps:ApplicationSessionTerminated http:/www.w3.org/2011/03/ws-evt/WrappedSinkPortType/NotifyEvent xs:any*
38、 aps:ApplicationSessionTerminated 22 Ecma International 2011E.4.3 Template of ApplicationSessionTerminated event notification to wrapped event sink of WS-BaseNotification http:/docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify xs:any* aps:ApplicationSessionTerminated Ecma International 2011 23
