Thanks Raymond. A few more questions ;-) - The xsd defines the name attribute for PolicyIntent and PolicySet as of type NCName. However we have model these in the model classes QNames. I am assuming that the namespace uri for all intents and policyset defined in a specific definitions.xml is the value of the 'targetNamespace' attribute of the 'definitions' element. Is this right?
- Can a qualified intent have its qualifiable parent intent belonging to a different targetnamespace. If so how would this be evident from the name of the qualified intent? For example if there is an intent a:intentOne and then there is a qualified intent over this like intentOne.intentTwo - how is to be inferred that intentOne belongs to a different namespace Thanks - Venkat On 7/31/07, Raymond Feng <[EMAIL PROTECTED]> wrote: > Hi, > > AFAIK, policySet can be used directly without going through intents. So a > policySet is still valid even it doesn't provide any intents. > > Please see the SCA Policy Framework Spec V1.0 starting from line 529: > > 529 Similarly, one or more policySets can be attached to any SCA element > used in the definition of > 530 components and composites. The attachment is specified by using the > optional @policySets > 531 attribute. This attribute takes as its value a list of policySet names. > 532 For example, > 533 > 534 <service> or <reference>. > 535 <binding.binding-type policySets="listOfQNames" > 536 </binding.binding-type>. > 537 </service> or </reference> > ... > > Thanks, > Raymond > > ----- Original Message ----- > From: "Venkata Krishnan" <[EMAIL PROTECTED]> > To: <tuscany-dev@ws.apache.org> > Sent: Tuesday, July 31, 2007 7:24 AM > Subject: [Spec Related] 'provides' attribute in PolicySet > > > > Hi, > > > > In the specs for the PolicyFwk, the xsds mention the 'provides' > > attribute for a 'policySet' as optional. If this attribute is not > > specified how does one figure out which intent a particular policySet > > actually provides for. Could somebody help me with clarity on this, > > please? > > > > Thanks > > > > - Venkat > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
