[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6102) Server deployment status synchronization improvements

[Dominik Pospisil (JIRA)]

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

Dominik Pospisil commented on JBIDE-6102:
-----------------------------------------

Yes, I understand the current concept of synchronization. But why not extend this concept not only to signal deployment status from tooling point of view but also from server point of view? I think this is what an user is really interested in.

> Assuming a coding error in your application leads to a deployment failure, marking the deployment
> as "republish needed" would, and has, confused users into continuously clicking 'publish' expecting
> something different to happen and wondering why it didn't occur. 

This could be solved easily. If the deployment is marked as failed, the tooling could prevent user to redeploy util a resource is changed.

> As for deployment from commandline and other workspaces, we would need to decide what
> exactly to show in the server view. Do we show every file listed in the deployment folder?
> quartz-ra.rar? jboss-local-jdbc.rar? etc etc? We've found that typically users do not want to see this. 

Not necessairly every file. Grouped listing based on deployment type - as it is in admin console -would be avesome. 

> Server deployment status synchronization improvements
> -----------------------------------------------------
>
>                 Key: JBIDE-6102
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6102
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>            Reporter: Dominik Pospisil
>            Assignee: Rob Stryker
>             Fix For: 3.2.next
>
>
> I can see couple of ways how the project deployment status could be improved.
> 1) Currently, project deployment status could get easily out of sync.
> Once the JBT successfully initiates project deployment, it always assumes that the deployment was successful. JBT does not detect deployment failures and If something went wrong it gets out of sync. JBT should check deployment result.
> Also, when a project is manually undeployed / deployed  from the server the change is not picked up by JBT.
> 2) The server view only displays deployments managed by JBT within current workspace. It would be nice if the user has an overview of projects/applications/resources deployed in different workspaces or externally. It would be really handy e.g. when a user often switches workspaces, deploy various project in different workspaces. It could prevent a user of being confused what actually is or is not deployed.

-- 
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