[
https://issues.jboss.org/browse/JBDS-1858?page=com.atlassian.jira.plugin....
]
Len DiMaggio reopened JBDS-1858:
--------------------------------
Sorry about all the confusion over this.
The original issue was that the user does need to create a SOA-P runtime, but that runtime
no longer (not since JBDS-1670 was fixed) needs to have that SOA-P runtime named
"jboss-soa-p-5.0"
It's a minor issue - but the readme should tell the user to create a SOA-P runtime -
the user can name the runtime whatever they want. Thanks!
ESB 5.0 quickstarts readme files instruct the user to only use a
specific runtime name - but that requirement is no longer needed
---------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1858
URL:
https://issues.jboss.org/browse/JBDS-1858
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: SOA Platform
Affects Versions: 4.1.1.M1
Environment: Version: 4.1.1.GA
Build id: v20110908-0132-H1012-GA
Build date: 20110908-0132
SOA-P 5.2, ER4
Reporter: Len DiMaggio
Assignee: Brian Fitzpatrick
Priority: Minor
Fix For: 4.1.1.M2
The readme files all say:
To run this example, you should create EAP server runtime
with the name is "jboss-soa-p.5.0 Runtime" in your workspace.
But that requirement was resolved in:
https://issues.jboss.org/browse/JBDS-1670
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira