[
https://issues.jboss.org/browse/JBDS-1670?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1670:
-------------------------------------
If this project example has to be executed on JBoss AS 5.1, it is enough to replace:
<property
name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50</property>
with
<property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50,
org.jboss.ide.eclipse.as.runtime.51</property>
in the project example xml file.
That will solve the following issues:
- the warning dialog won't show up
- the project example engine will set a corresponding runtime and its name
- projects will be imported without any compile error (if JBoss AS 5.1 and ESB 4.9 are
compatible with SOA-P)
There will be no need for a workaround.
Seeing "Target runtime jboss-soa-p-5.0 Runtime is not
defined." error - in spite of the name of the runtime being set - with JBDS + AS +
JBossESB
-------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1670
URL:
https://issues.jboss.org/browse/JBDS-1670
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Environment: Version: 4.0.0.GA
Build id: v20110216-1930-H239-GA
Build date: 20110216-1930
JBoss AS 5.1
JBossESB 4.9
Reporter: Len DiMaggio
Attachments: log, Screenshot-200.png, Screenshot-201.png, Screenshot-202.png,
Screenshot-203.png, Screenshot-204.png
With JBDS 4 GA + AS 5.1 GA and JBossESB 4.9, I'm seeing this issue with the ESB
examples
Regardless of whether the AS server runtime is named "jboss-soa-p-5.0 Runtime",
this error is raised:
Target runtime jboss-soa-p-5.0 Runtime is not defined.
See attached screenshots and .log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira