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

Fri Nov 1 12:08:02 EDT 2013

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

David Lloyd commented on WFLY-2422:
-----------------------------------

*Requirements* (edit as needed)

Essentially this implies that the EJB subsystem will have to become aware of the deployment EJB client context.  We should have a sort of "client context profile" notion in the EJB subsystem configuration.  Then jboss-ejb-client.xml can simply select a profile (and possibly supplement it with more direct connection information).

The EJB client context profile should contain a listing of discovery methods, though to start we'd only support one: static connection listing.

Deployments with a given selected profile will have those EJB receivers registered with the deployment EJB client context.

> 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