[jbosstools-issues] [JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-13445:
-------------------------------------

DeploymentModuleOptionCompositeAssistant has an interface used only internally and by rse.ui called IDeploymentPageCallback.  The interface is outdated, but basically was a hack interface that has some of the pieces that would be needed to enable deployment scanner additions for remote servers. 

Specifically, there is no clean API to discover server home depending on what 'mode' the server is in (local / rse).  For local, we currently just access the runtime directly. For remote, there are string-constant property keys, but as.core cannot access these string constants and so have no clean way to gain access to the values for remote server home / configuration name / etc. 

The interface in as.ui right now, was previously used for as < 7,  and when as7 was added, workarounds were added to the class. 

Either way, this type of interface needs to be accessible in core, not ui, so the entire premise is broken. This api should be removed and a new cleaner one added. I believe this UI class is the only consumer of the similar api, but other code could clearly be cleaned up. 

This would also help the (potential) addition of server modes to have a more clear workflow as well. 
                
> Enable possibility of deployment scanner additions for remote servers
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-13445
>                 URL: https://issues.jboss.org/browse/JBIDE-13445
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: server
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.1.x
>
>
> Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc.  There is a lack of api here, and that will need to be fixed before this issue can work.
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. 

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