Re: [sca-policy] [ISSUE 15] External attachment - Alternative Proposal

From
Rich.Levinson <>
Date
2008-07-21T16:23:46+00:00
ID
Thread
Re: [sca-policy] [ISSUE 15] External attachment - Alternative Proposal
To Mike, Ashok, et al,

I have been trying to follow the discussion on issue 15. I understand
that  there is something important here that must be decided
and I am trying to get a clear picture of what that is, but have
been having some difficulty which I will try to explain (possibly
others are in same boat, and maybe my dilemma and its
explanation will help get the issue more clear all around):

I think what would be very useful is to show the life cycle of
a scdl file from its creation thru the intents being applied thru
the intents being resolved and explaining what is going on
at each phase wrt this issue.

It doesn't have to be a complex example, maybe something
simple like adding confidentiality and integrity to the external
Reference to the StockQuote service in the composite from
the SCA-Assembly ppt presentation:

http://www.oasis-open.org/committees/download.php/26768/SCA_Plenary_SCA_Assembly.ppt

    <reference name=“StockQuoteService" promote="AccountServiceComponent/StockQuoteService">
        <interface.java interface="services.stockquote.StockQuoteService"/>
        <binding.ws port="http://example.org/StockQuoteService#
          wsdl.endpoint(StockQuoteService/StockQuoteServiceSOAP)"/>
    </reference>

One could quick describe how this scdl file came into existence - ex
someone created it using a sca-friendly xml tool.
(One might optionally say that pieces of the file could automatically
be generated by another tool that reads the .war file for example,
then selectively included in this composite)

Then one could say let's apply confidentiality and integrity to this
reference and insert the appropriate intents.

At this point I think we come to issue 15.

What I would like to see here is the state of affairs when it is time
to apply the concrete policies. Presumably the service has been
at least partially deployed and maybe someone is sitting at a
tool that says that it is time to apply policies to match these
intents.

Presumably one would have a list handy of possible policies,
possibly selected by their "provides" capabilities.

At this point it sounds, as I understand it, that issue 15 is
relevant. i.e. there are different scenarios that could happen
here when the concrete policy replaces the intent.

Let me know if this sounds like a useful course to pursue further.

    Thanks,
    Rich