[jbosstools-issues] [JBoss JIRA] (JBIDE-15313) Investigate how to handle Wildfly port multiplexing

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-15313:
-------------------------------------

 News so far:

1) The api we currently use (ModelControllerClient.Factory.create(etc)) has a signature that allows the protocol to be passed in, so if we can discover the protocol (or allow the user to set it) it can work

2) Even if you pick the incorrect protocol, Darran *thinks* the client will time out after 5 seconds, and the operation will fail. We will still need to close the connection, however. This should be tested heavily, since HTTP and Remoting differ in which side of the connection sends the first data - so get the wrong combo and both sides end up waiting.

3) The Factory.create(etc) method requires a String for protocol, and there is no clear list of values that I've found so far. Darran says: remote, http-remoting and https-remoting.  Testing will be required to verify this list


With these 3 things in mind, it seems the biggest question is how to discover the proper protocol from the user's configuration, and, how to display this in the UI.  Currently, the management port is grouped in with the ports, and it would not truly make sense to put a different setting there. However, if we move this out, where would it live? It's own section, alone?  That also seems difficult to agree to. 
                
> Investigate how to handle Wildfly port multiplexing 
> ----------------------------------------------------
>
>                 Key: JBIDE-15313
>                 URL: https://issues.jboss.org/browse/JBIDE-15313
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: server
>    Affects Versions: 4.1.0.Final
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Alpha1
>
>
> While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen. 
> This jira will investigate what's necessary and what may need to change. 

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