You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jakarta.apache.org by "Rony G. Flatscher (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/15 16:10:39 UTC
[jira] [Resolved] (BSF-19) Allow multiple case-independt event
names in the filter part of
BSFEventProcessor.processExceptionableEvent(...) and ...
[ https://issues.apache.org/jira/browse/BSF-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rony G. Flatscher resolved BSF-19.
----------------------------------
Resolution: Fixed
Fix Version/s: BSF-2.5
> Allow multiple case-independt event names in the filter part of BSFEventProcessor.processExceptionableEvent(...) and ...
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: BSF-19
> URL: https://issues.apache.org/jira/browse/BSF-19
> Project: Commons BSF
> Issue Type: Improvement
> Components: BSF-2.x
> Affects Versions: BSF-2.4
> Reporter: Rony G. Flatscher
> Assignee: Rony G. Flatscher
> Fix For: BSF-2.5
>
>
> Currently creating an event adapter one is able to either denote a specific action event (e.g. like "windowClosing") or leave it empty, which causes all events of an event group to process the event.
> There are use cases where more than one, but not all of the events of an event group should be processed.
> Improvement #1: allow a list of blank (or '+') delimited event names that should be processed.
> There is quite some confusion at times what the correct spelling resp. correct case of event names is. This is because the comparisons carried out are case dependent.
> Improvement #2: while comparing an event name use the case independent comparisons, such that the case of an event name does not need to match
> Both improvements need to be applied to BSFEventProcessor.processExceptionableEvent(...) and BSFEventProcessor.processExceptionableEventReturningEventInfos.processExceptionableEvent(...) .
> [PS: Have fixes locally, but would like to apply them in sequence by tackling one open Jira issue after another.]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org