[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:comment-tabpanel&focusedCommentId=13037072#comment-13037072 ] 

Wolf-Dieter Fink commented on WFLY-2422:
----------------------------------------

>From my point of view there are further issues to consider.

It is not common to have a bunch of remote-outbound-connection with different user and property setting, this will make the configuration complicated and will not work if clustering is used.
The current configuration does not take this into account each r-o-c need to have the parameters AND if the cluster will be implemented in the same way the properties need to be repeated here as well.
This seems unnecessary and the profile should have user and properties to override the r-o-c and a simple flag cluster=true/false to configure the cluster.

Another issue is that it is only one <profile> allowed in the jboss-ejb-client.xml.
A reason to have more profiles is that huge environments have different applications and one application might need more than one foreign ejb application, other might use a different combination. This approach is application oriented and each app need to have a unique profile to be flexible.

Let say app-main use appOne and appTwo; app-web use appOne and app-web2 use appTwo.
In this case each application need it's own profile and the configuration of remote-profile is repeated.

>From my point of view there are two possible approaches:
application oriented:
one profile in jboss-ejb-client.xml
the profile element allow to reference other profiles
target oriented:
jboss-ejb-client.xml allow multiple profile
A profile is target oriented and contains 'only' a bunch of outbound definitions which point to servers which have the same app-deployment or are within the same cluster

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