Bug 903720 - Unable to checkin error when installing samples to Guvnor with modeshape
Summary: Unable to checkin error when installing samples to Guvnor with modeshape
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: manstis
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-24 16:20 UTC by Radovan Synek
Modified: 2023-05-31 22:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
empty repository (8.35 KB, text/xml)
2013-01-24 16:20 UTC, Radovan Synek
no flags Details
server log (130.73 KB, text/x-log)
2013-01-24 16:22 UTC, Radovan Synek
no flags Details

Description Radovan Synek 2013-01-24 16:20:56 UTC
Created attachment 686850 [details]
empty repository

Description of problem:
After importing empty_repository.xml - see an attachment, the dialog box appear questioning whether you want to install the samples or not. When clicking "yes" the error appears: 400 unable to checkin.

See the attached server.log for the detailed error message.


How reproducible:


Steps to Reproduce:
1. configure BRMS.5.3.1 standalone with guvnor to use modeshape
2. start the server, log in, on the first "install samples" dialog, reject the instalation and import attached empty_repo.xml 
3. the dialog should appear again, this time choose installing samples
4. you should be able to see the error now, check server.log

Expected results:
installation of samples should finish without any error message

Additional info:
this feature worked before, definitely with BRMS-5.3.0

Comment 1 Radovan Synek 2013-01-24 16:22:15 UTC
Created attachment 686851 [details]
server log

Comment 2 Geoffrey De Smet 2013-03-05 13:40:11 UTC
Reassign to the guvnor team, now that I am working full time on planner. So these issues aren't forgotten.


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