[jira] [Resolved] (AMQ-3630) NetworkBridgeFilterFactory should be assigned to Queue not NetworkBridge

["Gary Tully (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3630.
-----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 5.6.1)
                   5.6.0
         Assignee: Gary Tully

The observation is correct, the filter should be evaluated per destination.
fix in http://svn.apache.org/viewvc?rev=1325735&view=rev
                
> NetworkBridgeFilterFactory should be assigned to Queue not NetworkBridge
> ------------------------------------------------------------------------
>
>                 Key: AMQ-3630
>                 URL: https://issues.apache.org/jira/browse/AMQ-3630
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>         Environment: 5.6.0 on the trunk
>            Reporter: SuoNayi
>            Assignee: Gary Tully
>              Labels: NetworkBridgeFilterFactory, network
>             Fix For: 5.6.0
>
>
> We can assign NetworkBridgeFilterFactory such as DefaultNetworkBridgeFilterFactory or conditionalNetworkBridgeFilterFactory for queue.But the source code on the trunk,class DemandForwardingBridgeSupport in fact, assigns NetworkBridgeFilterFactory to NetworkBridge,this causes DefaultNetworkBridgeFilterFactory will be applied at first even though specifying conditionalNetworkBridgeFilterFactory for the queue.The solution is making property filterFactory of DemandForwardingBridgeSupport to be a local variable in the method createNetworkBridgeFilter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira