Fw: PR comment: Re: Give us more examples about MembershipContentRule

[Ian Robinson <ian_robinson@uk.ibm.com>]

Kurosawa-san,
Thank you for your further comments; please accept our apologies for the
delay in responding.
The TC discussed your input and will provide the clarification detailed
below in the AppNotes document. I attach the full response of the TC below:


----------------------------------------------------------
The ServiceGroup specification refers only to normatively-defined
information in other specifications. For an interface name, therefore, only
the most derived type is defined by WSDL 1.1, and this is the name that
must be used in the MemberInterfaces attribute of the
MembershipContentRule.  In the example used in the comment email, it is the
name http://entry1.com/services/SomePortType  that should be used in the
MemberInterfaces attribute.
----------------------------------------------------------

We will also include suggestions of a best practice in the AppNotes
document
which answer the implied question about how to use the ServiceGroup
MembershipContentRule for derived portTypes.   This advice should be in a
new section dealing with ServiceGroups. Here is the text the TC has agreed
to:

---------------------------------------------------------
It may be convenient to build a ServiceGroup whose member services have
some aspect of common behaviour which is defined by the inclusion of
operations and properties from some common component portType.  Using the
behaviours defined by the ScheduledResourceTermination portType as an
example, the ServiceGroup may included a MembershipContentRule:

<wsrf-sg:MembershipContentRule
            ContentElements="wsrf-rl:TerminationTime"
      />

This constrains the content of every Entry to require a TerminationTime
element.  The service built on ServiceGroup should then require the
following (which are not normative requirements of the ServiceGroup
specification):
1) The corresponding member service also has the TerminationTime property
in its resource properties document  schema
2) The SetTerminationTime operation exists in the portType of the member
service.
3) The WSDL of the member service includes on the input element of this
operation the wsaw:Action attribute with the value: "
http://docs.oasis-open.org/wsrf/rlw-2/ScheduledResourceTermination/SetTerminationTimeRequest

"

These three requirements relate the content of the ServiceGroup Entry to
behaviour defined by the ScheduledResourceTermination portType.
--------------------------------------------------------



Regards,
Ian Robinson
WSRF TC co-chair

----- Forwarded by Ian Robinson/UK/IBM on 09/01/2006 11:50 -----



Comment from: masahiro.kurosawa.kc@hitachi.com

Name: Masahiro Kurosawa
Title: Re: Give us more examples about MembershipContentRule
Organization: Hitachi, ltd.
Regarding Specification: WS ServiceGroup 1.2 pr02
(
http://www.oasis-open.org/committees/download.php/14802/wsrf-ws_service_group-1.2-spec-pr-02.pdf
)
- - -
Thanks for your time and help on my question (Issue WSRF154).

About question #2 and #3, I completely understand. Thanks again for your
recommendations.

But, about question #1, I meant to say '{
http://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-ResourceLifetime-1.2-draft-04.wsdl}

ImmediateResourceTermination'. Intention of this question is:

- When a ServiceGroup WS-Resource wants its ServiceGroupEntrie WS-Resources
to support the operation(s) of ImmediateResourceTermination portType in
their portType

- and Name of that portTypes are actually something like '{
http://entry1.com/services}SomePortType',

- should it specify '{
http://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-ResourceLifetime-1.2-draft-04.wsdl}

ImmediateResourceTermination' in MemberInterfaces attribute, or '{
http://entry1.com/services}SomePortType'?


I think the former one is right because the names of portTypes are of great
variety and it's meaningless to specify '{
http://entry1.com/services}SomePortType'. But, I could not decide it.

Yes, I'll be able to understand after getting the examples.

Thanks.

Regards,
Ian Robinson
STSM, WebSphere Messaging and Transactions Architect
IBM Hursley Lab, UK
ian_robinson@uk.ibm.com