Allow use of message selectors for JMS transport
------------------------------------------------
Key: ESBJAVA-562
URL: https://wso2.org/jira/browse/ESBJAVA-562
Project: WSO2 ESB
Issue Type: Improvement
Components: Proxy Services Management
Reporter: Lucas Moten
Assignee: Asankha Perera
Priority: Minor
The JMS Listener does not currently support use of message selectors to allow
for filtering the messages it processes on a queue. However, custom properties
may be assigned messages that are placed on the queue as follows:
<property action="set" scope="transport" name="propertyname"
value="literal" />
To allow the ESB to make use of properties to determine whether to process a
message for mediation, forwarding, etc., it is recommended to support
messageSelectors when the consumer is created in JMSUtils. A possible
configuration for this could be:
<proxy name="myProxy" transports="jms">
<parameter name="transport.jms.ConnectionFactory"
locked="true">myQueueConnectionFactory</parameter>
<parameter name="transport.jms.Destination"
locked="true">myQueue</parameter>
<parameter name="transport.jms.MessageSelector"
locked="true">property='value'</parameter>
<target>
... sequences and mediators here ...
</target>
</proxy>
It is anticipated that a solution may impact the following files:
- org.apache.synapse.transport.jms.JMSConnectionFactory
- org.apache.synapse.transport.jms.JMSConstants
- org.apache.synapse.transport.jms.JMSListener
- org.apache.synapse.transport.jms.JMSUtils
-Lucas
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
