[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-7814) User is not notified when deployment fails

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-7814.
--------------------------------

    Resolution: Done


updates to server log view committed.  I've added a preference action which can also re-log errors to the Error Log. Also, now simply selecting a server anywhere in the workbench (most likely in server view) will update the server log view. 

Finally the annoying progress monitor dialog was replaced with background jobs so as not to annoy the user every time they select a new server. 

> User is not notified when deployment fails
> ------------------------------------------
>
>                 Key: JBIDE-7814
>                 URL: https://issues.jboss.org/browse/JBIDE-7814
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Libor Zoubek
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.2.0.CR1
>
>         Attachments: JBIDE-7814.jpg, serverlog.jpg
>
>
> AFAIK when deploying we are calling server via JMX. What happens when JMX call is not successful? Nothing good. Studio shows project as deployed, but app server in worse case does not know about deployment (when target dir is set to workspace), in better case notices it after a few seconds.
> User than can only guess what and why is his project not deployed.
> This confusing behavior can be simply reproduced on any soa-p server, since you have to uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to make JMX working. If you do not do that, you'll reproduce.
> AS Adapter should warn user on JMX call errors.

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