[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ] 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. -- 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