|
If you were logged in you would be able to see more operations.
|
|
|
BlazeDS
Created: 05/15/08 01:30 PM
Updated: 05/16/08 01:38 PM
|
|
| Component/s: |
Messaging
|
|
Security Level:
|
Public
(All JIRA Users
)
|
|
| Severity: |
Incorrectly Functioning
|
| Reproducibility: |
Every Time
|
| Discoverability: |
Medium
|
| Found in Version: |
BlazeDS 3.0.1
|
| Milestone: |
BlazeDS 3.0.1
|
| Affected OS(s): |
Windows
|
| Steps to Reproduce: |
MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using. This means that for customers using MessageService.pushMessageToClients(...), which is described in our docset and Javadoc to support custom adapters, messages are not routed to Consumers subscribed with a wildcarded suptopic. There's no workaround.
The method should be converting both of these strings to Subtopic instances and comparing them using the Subtopic#matches(Subtopic) method.
MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using. This means that for customers using MessageService.pushMessageToClients(...), which is described in our docset and Javadoc to support custom adapters, messages are not routed to Consumers subscribed with a wildcarded suptopic. There's no workaround.
The method should be converting both of these strings to Subtopic instances and comparing them using the Subtopic#matches(Subtopic) method.
|
| Language Found: |
English
|
| Bugbase Id: |
none
|
| Triaged: |
Yes
|
| Regression: |
No
|
| QA Owner: |
aglosban
|
| Resolved by: |
Seth Hodgson
|
| Participants: |
aglosban and Seth Hodgson
|
| JDK: |
Sun JDK 5
|
| Application Server: |
Apache Tomcat 6.x
|
|
All
|
Comments
|
|
Sort Order:
|
|
Bug
Closed
MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.
Customer confirmed fix.