[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-192) Refactor Replicator so it won't be forced to provide noop implementation for Distributor's methods.

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-192?page=all ]

Tim Fox closed JBMESSAGING-192.
-------------------------------

    Resolution: Done

> Refactor Replicator so it won't be forced to provide noop implementation for Distributor's methods.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-192
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-192
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core Distributed Support
>    Affects Versions: 1.0.0 alpha PR2 (clustered)
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.2.0.Alpha1
>
>
> A replicator doesn't really need to implement org.jboss.messaging.core.Router, since its receivers are remote. It only needs support for
> Set handle(DeliveryObserver observer, Routable routable, Transaction transaction)
> However, currently the easiest way to plug a Replicator into the ChannelSupport implementation is to declare it Router. Refractor this and split the Router interface (and ChannelSupport  implementation) in two distinct parts: MultiReceiver (or some other name) and Distributor.
> Look for UnsupportedOperationException in org.jboss.messaging.core.distributed.replicator.Replicator.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira