Re: [OSWorkflow] Adding workflow instance reference to transientVars

Le mer 25/06/2003 à 06:49, Hani Suleiman a écrit : 
> Oh, you mean the AbstractWorkflow class? Why? What would this gain you? 

An AbstractWorkflow instance is a thing I would have used. I have
multiple interacting workflow instances (typically a master workflow and
several slave workflows)

We have been talking about that use case with James Violette and Aníbal
Rojas on the mailing list about 2 weeks ago.

> I think it would add the potential for a LOT of bad things (eg, what if 
> a function calls an action which calls the function?) If you're needing 
> this, then I think you likely have a pretty bad design...
It seems to me that what I did is rather clean, but my opinion must be
biased :)

> It IS possible 
> via BasicWorkflow, but highly discouraged.
That's what I did.
It works, but I don't like to instantiate a new BasicWorkflow when I
could get an already instantiated AbstractWorkflow.

> On Wednesday, June 25, 2003, at 12:21 AM, Walter Chang wrote:
> 
> > 'entry' is a reference to WorkflowEntry, through that, i still not 
> > able to get to Workflow instance.
> >
> > Hani Suleiman wrote:
> >
> >> Isn't it already in there, with key 'entry'?
> >>
> >> On Tuesday, June 24, 2003, at 11:47 PM, Walter Chang wrote:
> >>
> >>> how about adding workflow instance reference to transientVars?  this 
> >>> way, functions, conditions, etc. can get to it without having to add 
> >>> it to inputs map when initializing workflow.
> >>>
> >>> walter
> >>>
> >>>


-- 
Thomas NGUYEN <[email protected]>
Open Wide



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php