Hi, You will find the purpose of the operation element in the PolicyFramework Specifications. The operation element is used at times when you want to specify 'intents' or 'policySets' that are to apply to only specific operations in a service. Specifying such intents and policysets at the service element level will make it apply to all operations of the service.
Hope this helps. - Venkat On Jan 30, 2008 7:38 AM, Jeff Davis <[EMAIL PROTECTED]> wrote: > Hi, > > I noticed that the type definition for "Service" contains an optional > child > element for "operation" (see below): > > <complexType name="Service"> > <sequence> > <element ref="sca:interface" minOccurs="0" maxOccurs="1" /> > <element name="operation" type="sca:Operation" minOccurs="0" > maxOccurs="unbounded" /> > <choice minOccurs="0" maxOccurs="unbounded"> > <element ref="sca:binding" /> > <any namespace="##other" processContents="lax"/> > </choice> > <element ref="sca:callback" minOccurs="0" maxOccurs="1" /> > <!-- > <any namespace="##other" processContents="lax" minOccurs="0" > maxOccurs="unbounded" /> > --> > </sequence> > <attribute name="name" type="NCName" use="required" /> > <attribute name="promote" type="anyURI" use="required" /> > <attribute name="requires" type="sca:listOfQNames" use="optional" > /> > <attribute name="policySets" type="sca:listOfQNames" > use="optional"/> > <anyAttribute namespace="##any" processContents="lax" /> > </complexType> > > What is this operation element for? I couldn't find any related > documentation in the Assembly Model Specification that describes its > purpose > (I tried a few things with it, but didn't see what impact it had). > > Thanks! > > jeff >
