[kepler-dev] [Bug 3539] New: - wierd behaviors of port parameter
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Thu Oct 16 14:32:13 PDT 2008
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3539
Summary: wierd behaviors of port parameter
Product: Kepler
Version: 1.0.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: director
AssignedTo: berkley at nceas.ucsb.edu
ReportedBy: jianwu at sdsc.edu
QAContact: kepler-dev at ecoinformatics.org
when put a port parameter in a composite actor, there are some wierd behaviors:
I put DDF/PN in top level and have an actor whose firingCountLimit is 2.
1) If DDF is set in composite actor, firingCountLimit of the first actor in the
composite actor is set 1 or other number, the actor is only fired once.
2) If DDF is set in composite actor, firingCountLimit of the first actor in the
composite actor is set NONE, the actor is fired for infinite times.
3) If no director is set in composite actor, firingCountLimit of the first
actor in the composite actor is set NONE, the actor is only fired once. Also
its value from the port parameter may be wrong.
I will attach the worflow later.
More information about the Kepler-dev
mailing list