Bug 974013
Summary: | Add kie-remote into BRE | ||
---|---|---|---|
Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Ryan Zhang <rzhang> |
Component: | Configuration | Assignee: | Kris Verlaenen <kverlaen> |
Status: | CLOSED WONTFIX | QA Contact: | Lukáš Petrovický <lpetrovi> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 | CC: | kverlaen, mrietvel |
Target Milestone: | --- | Flags: | rzhang:
needinfo+
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-07 15:09:57 UTC | 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: | |||
Bug Depends On: | 973913 | ||
Bug Blocks: |
Description
Ryan Zhang
2013-06-13 09:35:12 UTC
Kris, Thanks for pointing this out. I assume that we would include both kie-remote-client and kie-remote-service for both BRE and BPE(BPMS engine). Could we include these two modules in droolsjbpm-integrtion distribution? kie-remote-* is currently mostly targeted towards BPMS. Including it for BRMS as well might not be trivial: - kie-remote is based on jbpm-services etc., basically it depends on almost all core jbpm jars, including it would mean including almost all jbpm jars as part of BRMS - the session mgmt in jbpm-services is mostly targeted towards process or process+rules use cases, it might not be the best solution for pure rule use cases (as it will persist the session state after each command, which might not be ideal when a session can include a large amount of data - kie-remote-service is currently not included in kie-drools-wb (so either we would need to include it there as well, or the user would have to set up the REST service themselves somehow), the REST service itself is also targeted towards processes (rule functionality only available through the generic execute method) Kris As discussed on program call, since execution server for BRMS is different, I'll close this issue. |