[jbosstools-issues] [JBoss JIRA] (JBIDE-17824) Remote EAP 5 without a runtime does not have a default config

Martin Malina (JIRA) issues at jboss.org
Wed Jul 9 07:10:24 EDT 2014


     [ https://issues.jboss.org/browse/JBIDE-17824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina updated JBIDE-17824:
----------------------------------

    Labels: respin-a  (was: )


> Remote EAP 5 without a runtime does not have a default config
> -------------------------------------------------------------
>
>                 Key: JBIDE-17824
>                 URL: https://issues.jboss.org/browse/JBIDE-17824
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>            Priority: Minor
>              Labels: respin-a
>             Fix For: 4.2.0.Beta3
>
>
> When you create a remote EAP 5 server without a runtime, on the last page of the dialog called Remote System Integration, there are two fields:
> Remote Server Home
>  - it will be empty and you can browse for it - that's fine
> Remote Server Configuration
>  - this will be normally prefilled with "default" - probably taken from the runtime. But since we have no runtime, it will be empty. I would prefer if we could prefill "default" in this case, too. Also, when you leave it empty and click Test, it will tell you that the config is alright. So it seems under the hood we actually use "default" as the default (if I enter some nonsense, it will show an error).
> So it's more of a usability problem - users probably don't have to fill anything in and it will work with the default profile. But it's imho much better to have "default" there, because that makes it obvious what kind of input is expected.
> Note that the same applies when you change the profile of an existing (local) EAP 5 server. I assume that this is the same code.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the jbosstools-issues mailing list