Venkata Krishnan wrote:
Hi,
1) So for intents and policysets attached to implementation.xxx I understand
that you are proposing the addtion of another field in the Component model
to hold this information. i.e.
-List<Intent> getRequiredIntents() /* this will capture intents specified
at the component element level
so that
implementation, services and references inherit these */
- List<PolicySet> getPolicySets() /* this will capture policysets specified
at the component level
so that
implementation, services and references inherit these */
- List<Intent> getIntentsForImplementation(); /* for capturing intents
specied at the implementation
element level */
- List<PolicySet> getPolicySetForImplementation(); /* for capturing intents
specied at the
implementation element level */
If this is what you are suggesting, I am ok with this and will roll this
out.
I don't think that this is necessary. Component.requiredIntents and
components.policySets should be sufficient.
2) For Operations, please help me understand further what you are
proposing... if its Intent.getOperations and PolicySet.getOperations. Here
are some questions I have in mind with this...
i) this seems like Intent and PolicySets have Operations whereas
Operations are actually another kind of Intent / Policy attach point, very
much like composite, component, service, reference.. etc.
ii) to find out the bunch of intents that apply to an operation I'd have
to run thro all the Intents in the domain
I can't make sense of "all the intents in the domain". In my view,
intents are associated with a component, a service, a reference or a
property, and optionally apply to a list of operations.
iii) if Operation model instances are going to be shared then again what
intents or policysets are attached in the context of one service may not be
in the context of another service.
Correct, they have to be shared, and this is why storing intents under
operations, which you tried before, does not work.
Does this all make sense or am I missing something very fundamental here ?
Thanks for helping with your thoughts around this - I've been really needing
this for a while now :)
- Venkat
[snip]
Yes, it's tricky here. The operation-level intents/policySets can be
attached to different levels in the configuration:
(interface, operation)
(service, operation)
(reference, operation)
(binding, operation)
(implementation, operation)
(implementation, service, operation)
Are you proposing List<Operation> Intent.getOperations() and
List<Operation>
PolicySet.getOperations()?
Yes, I'm not only proposing, it's how it was initially coded, see line
62 of Intent.java. I've been repeating that I think it is the correct
way to model the Intent -> operations relationship. I guess I'm going to
stop repeating it as we've already experimented with different other
ways to model this and I'm sure it'll go full circle... back to where we
were on line 62 of Intent.java :)
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
