Bug 971065 - Updating asset's source via REST just replaces the source without creating a new asset version
Updating asset's source via REST just replaces the source without creating a ...
Status: NEW
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor) (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: manstis
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-05 11:18 EDT by Petr Široký
Modified: 2015-02-24 13:11 EST (History)
1 user (show)

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Široký 2013-06-05 11:18:33 EDT
Description of problem:
When updating the asset's source via Guvnor's REST API, the source is just replaced and the old source is not saved at all (e.g. no new version of the asset is created).

Looking at the source: https://github.com/droolsjbpm/guvnor/blob/5.3.x/guvnor-webapp/src/main/java/org/drools/guvnor/server/jaxrs/PackageResource.java#L743 it seems like a call to method asset.checkin() is missing.

Version-Release number of selected component (if applicable):
BRMS-5.3.1-P02

How reproducible:
Always

Steps to Reproduce:
1. Configure and the Guvnor.
2. Update the asset source via REST.
3. Login to guvnor and open the asset's metadata.

Actual results:
No new version is created after the source has been updated.

Expected results:
New version is created. The old source is saved within the previous version.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.