From: Michael
Rowley [mailto:mrowley@bea.com]
Sent: Monday, Oct 22, 2007 14:56
PM
To: sca-policy@lists.oasis-open.org
Subject: RE: [sca-policy] ISSUE 7:
Required intents on interfaces [Implicit addition of intents based on a service
or reference's @requires list]
The
policy spec should also describe why an intent should be placed on an interface.
I would propose something like the following:
“Intents
should be specified on interfaces when they should be seen by both the provider
and the client of the service and should be treated as part of the contract
between provider and the client.”
I
believe that the policy set selection algorithm also needs to be modified to
reflect these semantics. We could do this by adding a step between step
A2 and A3 which says:
A
2.5. If the target element is a binding, include all required intents
defined on the interface that provides the type for the service or reference
that the binding is on (i.e. follow this path:
binding->service->interface->@required).
Michael
From: Joshi,
Kaanu [mailto:Kaanu.Joshi@patni.com]
Sent: Wednesday, October 17, 2007
2:04 AM
To:
sca-policy@lists.oasis-open.org
Subject: [sca-policy] ISSUE
POLICY-7: Required intents on interfaces [Implicit addition of intents based on
a service or reference's @requires list]
Hi,
Please
find the link to the JIRA system: http://www.osoa.org/jira/browse/POLICY-7
The
subject has been modified to: Implicit
addition of intents based on a service or reference's @requires list
Regards,
Kaanu
Joshi
PS: In
conformance with newly adopted issues process.
From: Michael
Rowley [mailto:mrowley@bea.com]
Sent: Monday, October 08, 2007
9:12 PM
To:
sca-policy@lists.oasis-open.org
Subject: [sca-policy] NEW ISSUE:
Required intents on interfaces
TARGET: SCA Policy Framework Specification
DESCRIPTION:
The input specification to the SCA Assembly TC has the
following paragraph starting at line 900:
The @requires attribute can be applied to WSDL Port
Type elements (WSDL 1.1) and to WSDL Interface elements (WSDL 2.0). The
attribute contains one or more intent names, as defined by the
Policy Framework specification [10]. Any service or reference that uses an
interface with required intents implicitly adds those intents to its own
@requires list.
However, the policy framework
specification has no description of what it means for a policy intent to be
required by an interface. I believe this definition belongs in the policy
framework specification.
PROPOSAL
Add this paragraph (or something
similar) to the policy framework specification.
http://www.patni.com
World-Wide Partnerships. World-Class Solutions.
_____________________________________________________________________
This e-mail message may contain proprietary, confidential or legally privileged
information for the sole use of the person or entity to whom this message was
originally addressed. Any review, e-transmission dissemination or other use of
or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you have received
this e-mail in error kindly delete this e-mail from your records. If it appears
that this mail has been forwarded to you without proper authority, please
notify us immediately at netadmin@patni.com and delete this mail.
_____________________________________________________________________