Re: [Perl-workflow-devel] Making activity configs local to workflow/state?

[jonasbn <jo...@gm...>]

Hi Alex,

I understand and acknowledge the problem and I think it can be fixed.  
But I am concerned about backwards compatibility.

So perhaps the Workflow configuration should support local and global  
activities?

What do you think?

jonasbn
--
AIM: BjonasN      Gtalk: jo...@gm...
ICQ: 62401545   MSN: jo...@io...


On 21/11/2007, at 10.56, Alexander Klink wrote:

> Hi all,
>
> I've been stumbling over the fact that activity names are global
> a lot lately. For example, we have different workflows that have
> activities with the same name that should actually do different
> things.
> IMHO, activity names should be local to their workflow and (maybe?)
> even their state. What do you all think about it and if you agree
> with me, how would we go on to change the behaviour (possibly while
> still being backwards-compatible)?
>
> Best regards,
>  Alex
> -- 
> Dipl.-Math. Alexander Klink | IT-Security Engineer
>        ak-...@cy... | working @ urn:oid:1.3.6.1.4.1.11417
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Perl-workflow-devel mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel