[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-2708) TimerImpl prints out signalname rather than event name when a timer event is fired and hence the signalname is null

[Joram Barrez (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBPM-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joram Barrez resolved JBPM-2708.
--------------------------------

    Fix Version/s: jBPM 4.4
       Resolution: Done


Thanks for noticing! 
Probably a victim of copy pasting ....

> TimerImpl prints out signalname rather than event name when a timer event is fired and hence the signalname is null
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-2708
>                 URL: https://jira.jboss.org/jira/browse/JBPM-2708
>             Project: jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Runtime Engine
>    Affects Versions: jBPM 4.3
>         Environment: Eclipse 3.5, Vista, Oracle 11g, 
>            Reporter: Martin Porter
>            Assignee: Joram Barrez
>            Priority: Minor
>             Fix For: jBPM 4.4
>
>   Original Estimate: 1 minute
>  Remaining Estimate: 1 minute
>
> The TimerImpl class prints incorrect diagnostic message when a timer event is fired as it prints the signal name and not the event name. As per the lines in the code below:-
>     if (eventName!=null) {
>       ObservableElement eventSource = execution.getActivity();
>       if (log.isDebugEnabled()) log.debug("firing event "+signalName+" into "+eventSource);
>       execution.fire(eventName, eventSource);
>     }
> signalName should read 'eventName' instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira