[
https://jira.jboss.org/jira/browse/JBIDE-5890?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen moved JBDS-1109 to JBIDE-5890:
--------------------------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer
Studio))
Key: JBIDE-5890 (was: JBDS-1109)
Affects Version/s: 3.1.0.CR2
(was: 2.1.1)
Recognize/Set a SOA-P Server Runtime
------------------------------------
Key: JBIDE-5890
URL:
https://jira.jboss.org/jira/browse/JBIDE-5890
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.1.0.CR2
Reporter: Stelios Koussouris
Fix For: 3.2.next
[Stelios]
I have one more question. Why when you create a JBoss ESB Project it ONLY offers you the
chance to create an EAP Runtime and NOT and ESB Runtime? I create the ESB project and I go
to "Add Runtime" but it is an EAP Runtime "Type" that I end up with
(although I am pointing it to an
ESB Runtime).
[Max]
When you create an ESB project it needs an EAP runtime (SOA-P is an EAP) and the type if
we had one would be SOA-P (not just ESB).
The "runtime" you point to here is the complete server runtime (i.e. EAP), not
just ESB. Right now we unfortunately don't have a good check
if the underlying EAP includes an ESB runtime or not (like we i.e. have for Portal) this
is something we will need to work on going forward. The notion of ESB Runtime is something
we have for *standalone* ESB, not full platforms (like EAP and SOA-P).
To solve/align it better it would be major new functionality that would go into a JBDS
3.1 or even JBDS 4.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira