[jboss-jira] [JBoss JIRA] (WFLY-2976) The default of remote-outbound connections should be the same (http-remoting) as it is used in general for all other connections
Darran Lofthouse (JIRA)
issues at jboss.org
Thu Feb 20 07:27:47 EST 2014
[ https://issues.jboss.org/browse/WFLY-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12946328#comment-12946328 ]
Darran Lofthouse commented on WFLY-2976:
----------------------------------------
Within the CLI quite a bit of effort has gone into adding support for aliases and the set of rules for creating a complete URI from components so things like default scheme, default scheme if the port is 9990, deriving the port from the schema.
What would be good would be if we could find a way to pull all of this up from the CLI and make it re-usable by all components that establish connections.
> The default of remote-outbound connections should be the same (http-remoting) as it is used in general for all other connections
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2976
> URL: https://issues.jboss.org/browse/WFLY-2976
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Remoting
> Affects Versions: 8.0.0.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
> Labels: remote-ejb-connection, remoting
>
> EJB-client and ScopedContext use the http-remoting protocoll by default.
> It is confusing and not very handy to use a different default for the remote-outbound-connection configuration, here the native-remoting protocol is used.
> The default for this configuration should be http-remoting as well.
--
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
More information about the jboss-jira
mailing list