[
https://jira.jboss.org/browse/JBDS-1355?page=com.atlassian.jira.plugin.sy...
]
Brian Fitzpatrick reassigned JBDS-1355:
---------------------------------------
Assignee: Snjezana Peco (was: Brian Fitzpatrick)
Snjeza, I'm at a loss on this one. It's very easy to reproduce, and I suspect that
it has to do with the server runtime version. But if you create a SOA-P 5.1 server
configuration and use the EAP 5.0 configuration, I would think it would consider the
server to be "5.0" not "5.1".
At any rate, if I do the following:
1) Create a new EAP 5.0 server and point it at a SOA-P 5.1 ER3 runtime instance and call
it "jboss-soa-p.5.0 Runtime"
2) Go to Project Examples and select ESB for SOA-P 5.0 -> JBoss ESB HelloWorld Example
- ESB
3) The JBoss ESB Runtime and Server Library library variables in the project classpath are
marked as "unbound"
4) If I go in and select my runtime for both libraries (or server-provided in the case of
the ESB runtime), it compiles
So for some reason, the server I create with the name the example wants isn't
satisfying the requirement for:
<property
name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50</property>
Again, I think it's because it's a 5.1 runtime in reality even though it's
defined as a 5.0 runtime, but I don't know where to check for that.
Any ideas?
Import ESB examples - JBDS complains about runtime name - even if the
name is what the error message specifies
--------------------------------------------------------------------------------------------------------------
Key: JBDS-1355
URL:
https://jira.jboss.org/browse/JBDS-1355
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: SOA Platform
Affects Versions: 4.0.0.Beta1
Environment: Version: 4.0.0.Beta1
Build id: v201010052359R
Build date: 201010060016
Reporter: Len DiMaggio
Assignee: Snjezana Peco
Priority: Minor
Fix For: 4.0.0.Beta2
Attachments: runtime_name.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
See the attached screen shot - the run time was named just as JBDS specified - but the
error is still seen
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira