[
https://jira.jboss.org/jira/browse/JBIDE-3046?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-3046:
------------------------------------
tough call max. If their JMX is messed up, then the deployment location won't be added
properly and all sorts of other stuff won't happen. If we just "fall back"
without alerting the user, its no good.
AS credential question should not hide the reason
-------------------------------------------------
Key: JBIDE-3046
URL:
https://jira.jboss.org/jira/browse/JBIDE-3046
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.beta1
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Fix For: 3.0.0.CR2
If the server has jmx issues I get a dialog telling me a Security exception was thrown
with no info on the message nor any trace of it in the console or error log.
Making it very hard to debug what is the cause of it.
Maybe we should tell the user that JMX login might be disabled ?
--
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