RE: [sca-policy] ISSUE 52: Policy algorithm gets required intentsfrom wh

sca-policy message

Subject: RE: [sca-policy] ISSUE 52: Policy algorithm gets required intentsfrom what interfaces definitions/declarations?

From: "Joshi, Kaanu" <Kaanu.Joshi@patni.com>

To: Michael Rowley <mrowley@bea.com>, "sca-policy@lists.oasis-open.org"<sca-policy@lists.oasis-open.org>

Date: Tue, 29 Apr 2008 09:14:20 +0530

Hi folks,

A new issue has been created in the SCA Policy TC JIRA. The link to this issue is http://www.osoa.org/jira/browse/POLICY-52

Regards,

Kaanu Joshi

Expect A Miracle!

From: Michael Rowley [mailto:mrowley@bea.com]
Sent: Monday, April 28, 2008 11:48 PM
To: sca-policy@lists.oasis-open.org
Subject: [sca-policy] NEW ISSUE: Policy algorithm gets required intents from what interfaces definitions/declarations?

RAISER: Michael Rowley

TARGET: SCA Policy Framework Specification (CD01)

DESCRIPTION:

In section 4.10, step A has the following text:

A. Calculate the required intent set that applies to the target element as follows:

1. Start with the list of intents specified in the element's @requires attribute.

2. Add intents found in any related interface definition.

Step A2 here isn’t clear and we may also want to allow for intents to come from interface _declarations_ in addition to interface definitions.

There seems to be 4 possible sources of intents for interfaces:

1. The interface definition file (e.g. Java or WSDL) that is referenced from the component type.

2. The interface declaration for a service in the component type (i.e. <interface.java requires=”...”/>)

3. The interface definition file (e.g. Java or WSDL) that is reference from the component.

4. The interface declaration in a component (i.e. component/service/interface).

I believe that #3 from the above is new, based on the resolution of ASSEMBLY-39.

PROPOSAL

None.

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.