Bug 912771
Summary: | Creating a new SOA runtime should automatically create a jBPM runtime | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
Component: | Tooling | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.0 | CC: | soa-p-jira |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Len DiMaggio
2013-02-19 15:55:20 UTC
Max Rydahl Andersen <max.andersen> made a comment on jira JBDS-2472 this is not a bug, the server creation does not know about runtime detection which is the one that normally does this "wiring". I agree it would make perfect sense to have "subruntimes" detected/configured but that is currently not how it works. Koen Aers <koen.aers> updated the status of jira JBDS-2472 to Resolved Koen Aers <koen.aers> made a comment on jira JBDS-2472 As there will be no more new features on the jbpm 3 tooling and as per Max Andersen's comments it is not a bug but rather a new feature, I will resolve the issue as 'Won't Fix'. Feel free to reopen the discussion if this is not appropriate. |