[
https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin....
]
Brian Stansberry updated WFLY-2422:
-----------------------------------
Fix Version/s: 10.0.0.Beta1
(was: 9.0.0.CR2)
I'm moving this to 10.0.0.Beta1 as it's too late for 9.0.0 and 10 Beta1 is the
last 10.0 release for new features. If you don't expect this to be done by early
August, please unschedule or move to 11. If you expect it earlier and one of the
10.0.0.Alpha versions is appropriate, please schedule it for one of those.
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: 10.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.15#6346)