[
https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17103:
-------------------------------------
Right now if for some reason two handlers think they are supposed to
create a runtime, you will end up with two duplicate runtimes.
I believe this is actually intended, believe it or not. For example, when doing detect
runtime on a soa distribution, we actually expect both the AS handler and the ESB handler
to respond to a path and create their relevant models.
So this makes it pretty risky to change without fully understanding the rquirements and
workflow. THe last time I made large changes to runtimes, I tried my best to avoid
changing the API of the handlers at all, because I saw I did not understand fully the
workflow.
Tough choices.
No warning/error is shown when detected runtime fails to be added
-----------------------------------------------------------------
Key: JBIDE-17103
URL:
https://issues.jboss.org/browse/JBIDE-17103
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta2
When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by
the tooling, runtime detection usually detects it alright, but when you then click OK, the
runtime+server are not added. And there is no error anywhere at all - we should fix that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira