[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7287) Lsit of deloyed modules on Server Configuration Editor's Deployment tab is not updated right after new module is deployed

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-7287:
------------------------------------

The table is not actually a list of deployed resources, but a list of modules that *COULD* be deployed. Unfortunately, there's no event framework for when a new module is born. We only get when they're deployed. Since this list is meant to be a list of all current modules that *COULD* be deployed, we have to respond to all new modules as they're born, not as they're deployed.

So, without an event framework here, the best I could do is offer a refresh hyperlink under the table. Would this be sufficient? 

Sucks, I know. 

> Lsit of deloyed modules on Server Configuration Editor's Deployment tab is not updated right after new module is deployed
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-7287
>                 URL: https://jira.jboss.org/browse/JBIDE-7287
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Denis Golovin
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.2.0.Beta2
>
>
> 1. EXECUTE: Create: Server runtime, server instance
> 2. EXECUTE: Open Server configuration editor and select Deployment tab
> 3. ASSERT: It contains no modules in table at the bottom
> 4. EXECUTE: Create Dynamic Wed project and deploy it to the created server
> 5. ASSERT: Table in Server Configuration editor from step 3 should contain new deployed module
> Now it fails at 5th step

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