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

[Max Andersen (JIRA)]

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

Max Andersen commented on JBIDE-7814:
-------------------------------------

...and I will add that making all errors silent is not what we want and I believe we actually did show critical errors like this one before (i.e. not able to authenticate).

This does look like a rather big regression to what we had before (which also wasn't perfect either - but at least you knew as a user something went wrong)


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