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.
-ListIntent getRequiredIntents() /* this will capture intents specified
at the
Hi,
Basically there are two concepts:
1) The introspected implemention code (for example, a java class or a BPEL
file). Usually the metadata contributes to the corresponding component type
which is shared by all components that use the same implementation code.
2) The implementation.xxx
[snip]
Raymond Feng wrote:
We can have something like:
Well... You know what I think about how to model the intent -
operations relationship :) I think that you should experiment a bit with
what you're proposing, I'd like to just bring to your attention that:
- modeling operation and
More comments inline.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, October 22, 2007 6:16 PM
Subject: Re: Model intents and policySets attached under
implementation.xxx elements, was:Re: Transaction
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.
-ListIntent getRequiredIntents() /* this will capture intents specified
at the component element level
