Return-Path: 
 <tuscany-dev-return-27852-apmail-ws-tuscany-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-tuscany-dev-archive@locus.apache.org
Received: (qmail 79266 invoked from network); 30 Jan 2008 09:32:09 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 30 Jan 2008 09:32:09 -0000
Received: (qmail 64715 invoked by uid 500); 30 Jan 2008 09:31:59 -0000
Delivered-To: apmail-ws-tuscany-dev-archive@ws.apache.org
Received: (qmail 64512 invoked by uid 500); 30 Jan 2008 09:31:58 -0000
Mailing-List: contact tuscany-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:tuscany-dev-help@ws.apache.org>
List-Unsubscribe: <mailto:tuscany-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:tuscany-dev@ws.apache.org>
List-Id: <tuscany-dev.ws.apache.org>
Reply-To: tuscany-dev@ws.apache.org
Delivered-To: mailing list tuscany-dev@ws.apache.org
Received: (qmail 64503 invoked by uid 99); 30 Jan 2008 09:31:58 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2008 01:31:58 -0800
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of for.svkrish@gmail.com
 designates 209.85.146.178 as permitted sender)
Received: from [209.85.146.178] (HELO wa-out-1112.google.com) (209.85.146.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2008 09:31:32 +0000
Received: by wa-out-1112.google.com with SMTP id k22so318979waf.18
        for <tuscany-dev@ws.apache.org>; Wed, 30 Jan 2008 01:31:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        bh=D6m0HRygsBGzskuVflhUtJajMK1QUmDduD/qVkwohsw=;
        b=H3Nhu0v0eALkysIS2qMa9CsW2A3WISv9zXU1gafCe/JvwFuYz896kpZFNSUIpgOPFoW5l1xuSRgzn/cVm4k1onYKrMsZdygnB22LWOp01x8RjX7uAQ2AzzrdSkaEL4WwOldp4ZBjVYXaWEXFh0DvsHdUy8mTy/d3EX6FFEpAFB0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=DuBnmqM6Yy1rHd4nx8hD64Xp0c6iG3FV52EGS7Plg4UwlOw5SMR/RQSozLiynvhvFSoMzoJoxWwCyAGjmLzj8+PlAunQ3zbE40TANa/lhLNyLhiq539ZkpJFLmvu68R2HCkQ29oP3Jd2jqgtKi107BD07eGGkS7qM2C/OCIkp2k=
Received: by 10.114.173.15 with SMTP id v15mr623396wae.63.1201685498416;
        Wed, 30 Jan 2008 01:31:38 -0800 (PST)
Received: by 10.114.234.8 with HTTP; Wed, 30 Jan 2008 01:31:38 -0800 (PST)
Message-ID: <33e260400801300131v1481a43fy786cc6710df27767@mail.gmail.com>
Date: Wed, 30 Jan 2008 15:01:38 +0530
From: "Venkata Krishnan" <for.svkrish@gmail.com>
To: tuscany-dev@ws.apache.org
Subject: Re: Service's operation element -- what is it for?
In-Reply-To: <5f9d3eed0801291808o62a8b8f4x523b4bc28f44258c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_19074_14146368.1201685498411"
References: <5f9d3eed0801291808o62a8b8f4x523b4bc28f44258c@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_19074_14146368.1201685498411
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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 <jdavis@idalica.com> 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
>

------=_Part_19074_14146368.1201685498411--