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

Thu Oct 31 10:34:02 EDT 2013

    [ https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12826200#comment-12826200 ] 

jaikiran pai commented on WFLY-2422:
------------------------------------

David, to add a bit more context to this, this is the same requirement we discussed where the user application can just point to a logical name of outbound connection(s) group. And that group can have N number of connections which can be dynamically updated via management APIs and the user application doesn't have to be bothered to updated its deployment descriptor to take into account the new nodes that possibly get added.

IMO, this is a valid requirement.

> Simplify the remote-outbound connections
> ----------------------------------------
>
>                 Key: WFLY-2422
>                 URL: https://issues.jboss.org/browse/WFLY-2422
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: EJB, Remoting
>    Affects Versions: 8.0.0.Beta1
>            Reporter: Wolf-Dieter Fink
>            Assignee: David Lloyd
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira