Bug 1087941
| Summary: | JSON entities are not un/wrapped in the REST API | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Ivo Bek <ibek> |
| Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ivo Bek <ibek> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.2 | CC: | etirelli, kverlaen, lpetrovi, mrietvel, rrajasek, rzhang, smcgowan |
| Target Milestone: | ER3 | ||
| 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: | 2014-08-06 19:54:33 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: | |||
|
Description
Ivo Bek
2014-04-15 16:13:16 UTC
Fixed. Commits: 6.0.x: https://github.com/droolsjbpm/drools-wb/commit/21e36abd master: https://github.com/droolsjbpm/drools-wb/commit/7315a725 *PLEASE NOTE*: The jackson-mapper-asl and jackson-xc dependencies should be added to the BRMS artifacts if they are not already present there! Re: jackson-mapper-asl and jackson-xc dependencies. I'm now noticing that those jars are installed with AS7/EAP6 as part of the modules. However, in my arquillian tests using AS7, deploying the (drools-wb) war to test this issue would fail because ClassNotFoundExceptions thrown for classes that are in those 2 jars. Uhm..?? I guess they don't need to be added then? Ivo, you're the reporter here, please verify. Verified in BRMS 6.0.2.ER2. This works because the smoke tests passed. We've decided to revert the commits that fixed this issue and BZ 1050894. Since it's been done for both BPMS and BRMS, this issue should still be solved. However, the code has changed, which is why I'm reopening this issue. Since the commits that changed this on *both* BPMS and BRMS have been reverted, this problem should still be fixed. Setting to MODIFIED so that QA can verify. Verified in BPMS 6.0.2.ER3 |