[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4374) Modules / deployment page

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-4374:
------------------------------------

1)  I really hate making UI's where depending on what you select in a combo, whole portions of widgets below them disappear or re-appear. I dislike coding them and I dislike using them ;) 

If the fix from WTP doesn't come soon enough or won't make it into our build, I can change the model into an XML string (as currently happens) and persist it in the server object instead of its own file. However I do not like that idea and would rather it be in its own file. 

The way WTP / tomcat does it is that they basically have just one "configuration" file which is actually used by the server. Their editor actually sets it inside the Server delegate object, and then the delegate persists its one "configuration" file. This wouldn't exactly work for me as each piece of functionality I add tends to be separate from others with no crossover. Also the files I'm persisting are not to be used by the server but are rather just for tooling. 

For now I'll switch to persisting inside the server object as an XML string but I don't particularly like it or think it belongs there. I'll mark this bug as solved, and I'll open a new one (trivial / later)  to migrate the preference to its own file if and when we get the patch from upstream

> Modules / deployment page
> -------------------------
>
>                 Key: JBIDE-4374
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4374
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.1.0.GA
>
>         Attachments: JBIDE-4374.jpg
>
>
> Create a Modules page in the server editor where you can specify the deployment location of each module you'll be deploying. This is due to the usecase where you need one module deployed to the default server location (for guaranteed early startup) but another to the separated metadata or custom location. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira