Bugzilla – Full Text Bug Listing
| Summary: | [DI] [UI]EventObjectSupplier doesn't work with wildcards in topic names | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Simon Chemouil <eclipse> | ||||||
| Component: | E4 | Assignee: | Project Inbox <e4.runtime-inbox> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | ob1.eclipse | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 173572 [details]
Fix for the EventObjectSupplier
This patch fixes the problem by remembering the topic on which the requestor subscribed, rather than finding the full topic name from the received event.
Simon, could you attach a patch against CVS Head? The patch seems to be using Git something-or-other. Also, could you make a JUnit to make sure that the problem stays fixed? Created attachment 173589 [details]
Patch
Patch against CVS Head + JUnit + updated the UIEvent counterpart and its test.
Patch applied to CVS Head. Thank Simon for finding this out and providing the fix! (In reply to comment #2) > Simon, could you attach a patch against CVS Head? The patch seems to be using > Git something-or-other. > > Also, could you make a JUnit to make sure that the problem stays fixed? I didn't see this earlier, thanks for applying the patch! (I'll provide my future patches in the appropriate format). |
Build Identifier: I20100705-2033 The OSGi spec allows to specify wildcards in topic names, ie, for an action group my/company/{ACTION1,ACTION2} one can listen on "my/company/*". When using a wildcard in the topic in the @EventTopic annotation, the event is received but the Supplier can't find it back, and supplies null to the requestor. The same problem exists with UIEventTopic / UIEventObjectSupplier Reproducible: Always