[jboss-jira] [JBoss JIRA] (WFLY-2422) Simplify the remote-outbound connections

[Wolf-Dieter Fink (JIRA)]

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

Wolf-Dieter Fink reopened WFLY-2422:
------------------------------------


At the moment the remoting-profil only work if the target is not a cluster.
If the client-context (jboss-ejb-client.xml) switch from the former configuration to <profile> it will not possible to add clusters element (TBH this is not wanted)
But the server side configuration does not allow to add a cluster configuration.

As a result the RemotingConnectionClusterNodeManager will not be able to install the cluster view.

An example can be found here
https://github.com/wfink/quickstart/compare/ejb-multi-server-remote-profiles

> Simplify the remote-outbound connections
> ----------------------------------------
>
>                 Key: WFLY-2422
>                 URL: https://issues.jboss.org/browse/WFLY-2422
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB, Remoting
>    Affects Versions: 8.0.0.Beta1
>            Reporter: Wolf-Dieter Fink
>            Assignee: Tomasz Adamski
>             Fix For: 9.0.0.Beta1
>
>
> At the moment the application need to reference each outbound connection with a remote-ejb-receiver element in the jboss-ejb-client.xml.
> But from an application perspective it is not relevant whether the server environment provide one or many receivers or whether the ejb-receiver is a cluster.
> It should be possible to add many outbound-socket-binding-ref elements and related properties to the remote-outbound-connection element of the server configuration.
> In this case it is possible to keep the application deployment independent from the server environment.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)