[kepler-dev] validateSettables in Manager

[Efrat Frank]

Dear Edward,

Thanks for your response.

The ProvenanceExecutionListener is a workflow component that listens  
to the director and reports firings and tokens sent/received events.  
Making this component extend the TypedAtomicActor would record its  
own firings and in some case it can be running indefinitely (e.g.,  
under PN).

I need to make it extend some workflow component in order to add it  
to apply it to a specific workflow and register it to listen to  
actors and ports in the beginning of a workflow execute (or during a  
change request). Any suggestions?

Thanks a lot,
Efrat

On Oct 19, 2006, at 10:24 PM, Edward A. Lee wrote:

>
> Probably you should extend TypedAtomicActor instead of  
> AbstractSettableAttribute
> and perform intialization functions in initialize().  Attributes do  
> not generally
> have initialization functions....
>
> Edward
>
> At 10:29 PM 10/17/2006, Efrat Frank wrote:
>> Dear hackers,
>>
>> I've noted that '_container.validateSettables()' in the Manager  
>> has been commented out for performance related issues. We've been  
>> using it in Kepler to initialize the ProvenanceExecutionLister  
>> (which extends AbstractSettableAtribute) and also to add an  
>> execution listener. I was wondering if there is any alternative  
>> way to call _container.validateSettables() in the beginning of a  
>> workflow execution or perhaps the ProvenanceExecutionListener  
>> should not extend AbstractSettableAttribute (it is a workflow  
>> settable attribute). Any ideas what could be a suitable replacement?
>>
>> Thanks,
>> Efrat
>
> ------------
> Edward A. Lee
> Chair of EECS and Robert S. Pepper Distinguished Professor
> 231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
> phone: 510-642-0253, fax: 510-642-2845
> eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal