[jboss-jira] [JBoss JIRA] Updated: (JBAS-2870) Separate the HA aspect from the invoker proxy

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated JBAS-2870:
-----------------------------------

    Fix Version/s: Backlog
                       (was: JBossAS-5.0.0.CR2)
          Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration]  (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)])


Unscheduling this for AS 5.0.0. It's a major rework of legacy code.

> Separate the HA aspect from the invoker proxy
> ---------------------------------------------
>
>                 Key: JBAS-2870
>                 URL: https://jira.jboss.org/jira/browse/JBAS-2870
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: Backlog
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Comment from Scott Stark (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926369#3926369)
> HA proxy invokers like JRMPInvokerProxyHA should not exist. The only difference between an ha proxy and regular proxy would be an interceptor that selected from the available targets and set the invocation proxy such that the common Invoker proxy was told the transport proxy to use. Even an unclustered proxy could have a recover/ha sematic like blocking until the server is availble with this configuration. HA is an aspect that should not be embedded in the transport specific proxy.

-- 
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