Venkat,
Not exactly sure what you're saying here, but I'll try to help.
First, in general if a component reference has an intent attached and it
gets promoted by some composite reference, the intent applies to the
composite reference.
If the promoting composite reference has one or more intents applied to
it, then those intents get added to any intents from the promoted
component reference. Let's assume no clashes of intents (in which case
it's an error).
The basic idea is true for the intents applied to operations within the
interface. They get promoted too - but are applied only to the
operations they are attached to. Same merging idea applies as well, if
there are intents on the composite reference.
Does that short explanation help?
The kind if scenario this supports is where for performance reasons only
one or two operations in a service need encryption and all the rest are
left unencrypted.
Yours, Mike.
Venkata Krishnan wrote:
Hi,
Looking at getting the policies working on operations of services I am
missing out on what is to be done for the following: -
- For operations on composite services when operations are defined in the
component service that is being promoted by this composite service. Right
now, I aggregate the operations in the component service over to the
composite service. Where the composite service specifies an operation
already specified in the component service, I have aggregated the intents
and policysets from the component service operations over to the composite
services'. The same has been done for references as well. Is this a right
thing to do ?
If somebody has better clarity on this please help.
Thanks
- Venkat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
