|
From: <jm...@so...> - 2002-03-05 14:25:34
|
Done, as I said
On Tue, 5 Mar 2002, Juli=E1n Mu=F1oz wrote:
>
> When there is no route in the Openflow, we have this not nice error (see
> below)
>
> I solved this in my cvs branch raising a "No Route" exception.
>
> Uhm, I think it should be the same here. If an instance of a process has
> no route to go, the activity should not be set autofinish. So this is an
> error in the design of the workflow.
>
> An error like "Workflow error. The process don't know what to do know (no
> transitions to follow)" would be more convenient.
>
> But where raise this exception ?
>
> openflow.forwardWorkitem ?
> openflow.getTransitionList ?
> process.route ?
>
> I think it is better in openflow.forwardWorkitem, do you agree ?
>
>
>
> Error Type: UnboundLocalError
> Error Value: local variable 'transition_list' referenced before assignmen=
t
>
> (...)
> File E:\Archivos de
> programa\zwinssl2\lib\python\Products\Openflow\openflow.py, line 523, in
> forwardWorkitem
> (Object: LockableItem)
> File E:\Archivos de
> programa\zwinssl2\lib\python\Products\Openflow\openflow.py, line 504, in
> getTransitionList
> (Object: LockableItem)
> UnboundLocalError: (see above)
>
>
>
>
>
--=20
__o
_ \<_
(_)/(_)
Saludos de Juli=E1n
EA4ACL
-.-
Foro Wireless Madrid
http://opennetworks.rg3.net
|