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: BSF
Issue Type: Improvement
Affects Versions: BSF-2.4
Reporter: Rony G. Flatscher
Assignee: Rony G. Flatscher
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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
