[esb-issues] [JBoss JIRA] Closed: (JBESB-2586) DefaultJMSPropertiesSetter should filter out all JMS vendor specific properties
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Fri May 22 10:27:57 EDT 2009
[ https://jira.jboss.org/jira/browse/JBESB-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Conner closed JBESB-2586.
-------------------------------
Resolution: Done
Updated in revision 26697.
> DefaultJMSPropertiesSetter should filter out all JMS vendor specific properties
> -------------------------------------------------------------------------------
>
> Key: JBESB-2586
> URL: https://jira.jboss.org/jira/browse/JBESB-2586
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.4 CP2
> Reporter: Kevin Conner
> Assignee: Kevin Conner
> Fix For: 4.4 CP3
>
>
> JBESB-2287 introduced filtering into the DefaultJMSPropertiesSetter but this is only usable in certain circumstances.
> One area which cannot use this, at present, is the JmsCourier created from EPRs. Listeners can therefore introduce properties which should be filtered.
> We are already filtering out all JMS Header properties, that is properties that start with JMSX.
> We should also be filtering out JMS Vendor specific properties, that is properties that start with JMS_. These properties can be read-only and there will be no way for us to re-set them when sending outbound JMS Messages so it makes no sense extracting them either.
--
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
More information about the esb-issues
mailing list