Model intents and policySets attached under elements, was:Re: Transaction policy seed code and questions on the Tuscany policy framework

[Raymond Feng]

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> element inside the component declaration. It's 
used to configure a component. And the information pertains to the declaring 
component only.

+1 on Sebastien's proposal to hold the implementation-level 
intents/policySets in the Component model. The component:implementation is a 
1:1 relationship so we don't have to define an extra model to represent 2). 
The method component.getImplementation() returns information for 1) today.

We can have something like:

public interface Component extends PolicyAttachPoint {
...
   // List<Intent> getRequiredIntents(); // from PolicyAttachPoint
   // List<PolicySet> getPolicySets(); // from PolicyAttachPoint
   List<OperationPolicyAttachPoint> getOperationPolicyAttachPoints();
}

public interface OperationPolicyAttachPoint extends PolicyAttachPoint {
   String getOperation();
   String getService();
   void setOperation(String operation);
   void setService(String service);
}

Thanks,
Raymond

----- Original Message ----- 
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Monday, October 22, 2007 11:55 AM
Subject: Re: Transaction policy seed code and questions on the Tuscany 
policy framework


[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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]