[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17103: ------------------------------------- This would require some significant changes in the API. As of now, there are several "runtime detectors". The one for AS is only one of them, but there are others. Currently, when the wizard / dialog is opened, it gets a set of RuntimeDefinition objects, but it does not keep track of which extension is providing each one. In the end, it takes a full set of RuntimeDefinition objects and asks each handler to try to create that runtime. If one handler cannot, it is expected to simply ignore it, not return an error. This is because it's possible other handlers may be able to create it. For example, if a RuntimeDefinition representing a seam runtime is passed to the AS handler, the AS Handler is expected to simply ignore it. The IRuntimeDetectorDelegate.initializeRuntimes(List<RuntimeDefinition> runtimeDefinitions) has no return type, and is in fact a void method. It's signature also does not allow throwing an exception. So this would require some substantial changse to the workflow. It also could break Seam tools, since seam also provides a IRuntimeDetectorDelegate for detectng and creating seam runtimes. -- 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