| Summary: | Attempt to rename package via REST results in a corrupted repository | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Lukáš Petrovický <lpetrovi> |
| Component: | BRM (Guvnor) | Assignee: | Mark Proctor <mproctor> |
| Status: | VERIFIED --- | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | BRMS 5.3.0.GA | CC: | mproctor |
| Target Milestone: | --- | ||
| Target Release: | BRMS 5.3.0.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Lukáš Petrovický
2011-11-24 09:34:42 UTC
The last paragraph should have read: "The problem is persistent even if you restart the server. The only way to get rid of it is to delete the repository." Hi could you please paste the code you used to rename package? Renaming package through REST is not supported yet even on the master branch. Thanks. Hello Jervis, the code is a little too complicated to paste here. But here's what I do: 1) Obtain a Package POJO from the RESTful API, ideally via XML as that's the most stable from my experience. 2) Change the title of the package in the POJO. 3) Send the POJO back via the RESTful API. 4) Observe the above exception. I'll try to simplify my code to provide a reproducer. I think I've got the idea. I will let you know if I need the client code. At the moment, this information should be enough for me to move forward. One more thing, as a matter of fact, the REST interface via Atom is actually far more stable. The REST interface via json and XML part of code was contributed by community members originally, and are not very well tested and maintained. (In reply to comment #4) > One more thing, as a matter of fact, the REST interface via Atom is actually > far more stable. The REST interface via json and XML part of code was > contributed by community members originally, and are not very well tested and > maintained. My personal experience is different: - the Atom API is missing some data that the XML one has. (bug 756671) - and the JSON interface has some problems with collections, which I have yet to report. (After I am able to find the root cause.) Fixed on both 5.3.x and master branch. This test has some client example codes that we used to test the REST service: https://github.com/droolsjbpm/guvnor/blob/4acab88936d812aa62e0d218ab68cbf6322e5186/guvnor-webapp-drools/src/test/java/org/drools/guvnor/server/jaxrs/BasicPackageResourceTest.java Please verify the issue on 5.3 ER4. VERIFIED |