[
https://jira.jboss.org/jira/browse/JBMESSAGING-1744?page=com.atlassian.ji...
]
Noel Rocher updated JBMESSAGING-1744:
-------------------------------------
Description:
I'm on-site with a customer who is soon going to production.
They have designed their application using JMS Selectors on distributed queues.
We all know this is a broken design but my point is that I think this should be
explicitely written in the doc.
Moreover, GSS is talking about an "unsupported configuration" see case # 348290
(
https://enterprise.redhat.com/issue-tracker/?module=issues&action=vie...).
was:
I'm on-site with a customer who is soon going to production.
They have designed their application using JMS Selectors on distributed queues.
We all know this is a broken design but my point is that I think this should be
explicitely written in the doc.
Moreover, GSS is talking about an "unsupported configuration" see case # 348290
.
More documented warnings on the usage of JMS selectors
------------------------------------------------------
Key: JBMESSAGING-1744
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1744
Project: JBoss Messaging
Issue Type: Task
Components: Documentation and Training
Environment: EAP 4.3 CP06 / 1.4.0.SP3-CP08.patch01
Reporter: Noel Rocher
I'm on-site with a customer who is soon going to production.
They have designed their application using JMS Selectors on distributed queues.
We all know this is a broken design but my point is that I think this should be
explicitely written in the doc.
Moreover, GSS is talking about an "unsupported configuration" see case # 348290
(
https://enterprise.redhat.com/issue-tracker/?module=issues&action=vie...).
--
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