[
https://issues.jboss.org/browse/JBIDE-23266?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-23266.
---------------------------------
Resolution: Rejected
Unfortunately there's no way to fix this. The current error dialog is because I
throw a CoreException during the launch. I do this intentionally, however, because if I
don't, a generic error dialog shows up which only says
{code}
"Starting Container Development Environment" has encountered a problem:
Server Container Development Environment has failed to start."
{code}
This message is a default message any time a server's "launch" has been set
to "starting" and then later set to "stopped". It's an automatic
message and cannot be prevented. It can, however, be superceded if we throw our own
CoreException which opens a more informative dialog.
You may think of a clever workaround: how about if we don't set it to starting at
all, until AFTER we have all the info we need, and know the user didn't cancel? Well,
WTP has us blocked there. If we are asked to 'start' the server, and our launch
method returns without setting the server to starting, the same error dialog appears.
Basically,
1) if we don't set server to "starting", WTP will show error.
2) If we do set it to starting, but then to 'stopped' after, WTP will show
error
3) There exists no way to suppress an error dialog,
4) Our CoreException is a bit more informative than what WTP shows.
Sucks to say, but there's no real workaround for this at all.
CDK Server adapter: keeps starting CDK not aborting it when cancel
button is pushed
-----------------------------------------------------------------------------------
Key: JBIDE-23266
URL:
https://issues.jboss.org/browse/JBIDE-23266
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.2.AM1
Reporter: Jeff MAURY
Assignee: Rob Stryker
Priority: Trivial
Labels: cdk, server
Fix For: 4.4.2.AM2
When the credential dialog is show when starting the CDK server, if the user push the
Cancel button, then an error dialog is then show where the operation should be aborted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)