Bug 1085958
| Summary: | The kie-services-client can not be used with OSGi | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Marco Rietveld <mrietvel> |
| Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> |
| Status: | CLOSED DUPLICATE | QA Contact: | Marek Winkler <mwinkler> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.1 | CC: | dvanbale, etirelli, kverlaen, mrietvel, rrajasek, smcgowan |
| Target Milestone: | --- | ||
| Target Release: | 6.0.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-09-14 12:02:21 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marco Rietveld
2014-04-09 18:03:32 UTC
Unfortunately, the hornetq-jms-client dependency can not be used on OSGi. From what I can find, hornetq hasn't made OSGi a priority and none of the hornetq artifacts can be bundled. Moving to another (OSGi compatible) jms client implementation at this phase in 6.0.2 is not a risk worth doing for this issue, so I'd like to defer it to 6.1 or later. At that point, we can move from hornetq to activemq, which does support OSGi. In short, please remove the blocker status for this bug because the scope of the work to fix it, is far greater than initially estimated. My apologies for this. I believe the remote client can be used with OSGi when using REST, so this applies only to JMS, correct? It applies to the kie-remote-client, as a module. The challenge at the moment is creating tests to verify and isolate problems. Moving to 6.2 as this was not a requirement for 6.1, further testing will need to be done to verify this all works. *** This bug has been marked as a duplicate of bug 1236636 *** |