[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7614) Add third column to deployment page to rename the output file / folder.

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-7614:
------------------------------------

Yes Fred... as mentioned in the bugzilla, your problem is a complex mix of jeetools and servertools. I'm not sure it requires API changes, but, I did fiddle with that stuff once nad it ends up breaking dozens of wtp tests... 

Max: You do not need to specifically type in a deploy name. The API populates the UI with the default for you. The question here is whether it's ok to put it into two columns, or if I require the creation of a third. 

As for things like BPEL... well... I guess the UI breaks down there, but I can't think of any way to handle all use cases and still solve the major one. Seriously... I've racked my brain for excessive periods of time over the past year and cannot come up with a single UI to handle outlying cases like BPEL.  In the BPEL case, the publisher chooses to ignore information set in some models. The publisher has the last final say on what to do and it chooses to ignore certain options. 

The entire case of the BPEL situation really messes up any possibility for a uniform UI. 

> Add third column to deployment page to rename the output file / folder. 
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-7614
>                 URL: https://issues.jboss.org/browse/JBIDE-7614
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.2.1
>
>         Attachments: JBIDE-7614.patch
>
>
> Currentlyu you can only update what folder a deployment goes to but you cannot at the last minute rename a deployment. Adding this third column should allow renaming of the final deployment.
> This will also be a good time to find any and all places (like explore utils) that do NOT use the proper API to find out based on settings where a module should be deployed to (or undeployed from). 
> Test this heavily and don't break shit...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira