[snip]
Venkata Krishnan wrote:
Hi Raymond,
Please see my comments inline.
Also, now that you are with this, may I request your views on the problem
that I am facing with attaching intents and policysets on implementation
model instances. Presently, atleast for the JavaImplementation model
instances we reuse instances across components. i.e. assuming we have CompA
and CompB using the same java implementation, then the implementation model
instance that we create is just one. This is a bit of a problem when CompA
and CompB have different intents specified and the underlying
implementations must inherit that. Please see
http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg24574.html
Thanks
- Venkat
I still think that a proper logical model (independent of its XML
representation) for policies inside component declarations is:
- policy intents on <implementation.xyz>, store them in the
Component.requiredIntents list
- policy intents associated with operations, have a list of operations
on the Intent
Let me know if you want me to prototype it, as we can discuss this at
length in email but only code will show if a model or another is the
right one for this.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
