Bug 827409 - Saving an empty process is not possible if the asset name has a space
Summary: Saving an empty process is not possible if the asset name has a space
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER9
: BRMS 5.3.0.GA
Assignee: Kris Verlaenen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-01 11:52 UTC by Toni Rikkola
Modified: 2025-02-10 03:20 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:20:02 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Toni Rikkola 2012-06-01 11:52:42 UTC 
Description of problem:
Using jBPM web editor in BRMS.

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


How reproducible:
Easy

Steps to Reproduce:
1. Make a new bpmn2 asset
2. Name it "My Asset"
3. Try to save
  
Actual results:
Tell me to check the server logs and validate. I validate and nothing happens.

Expected results:
I would like it to save.

Additional info:
Did some digging. The reason is that the asset name has a space in it and the asset name is used as the process id. The id can not have spaces.
Comment 1 Tihomir Surdilovic 2012-06-01 13:45:46 UTC 
Reproduced, fixing now.
Comment 2 Tihomir Surdilovic 2012-06-01 14:39:17 UTC 
Fixed committed to Designer master. Let me know if/when this becomes a blocker so can move to the product 2.2.x branch.
Comment 3 Tihomir Surdilovic 2012-06-05 14:50:44 UTC 
Fix now in Designer production (2.2.x) branch as well.
Comment 4 Ryan Zhang 2012-06-13 09:32:39 UTC 
This issue's fixes  have been picked by ER9. Please verify them on ER9.
Comment 5 Sona Mala 2012-06-19 10:06:08 UTC 
Verified for ER9. Asset name is converted to ID without spaces.
Comment 10 Red Hat Bugzilla 2025-02-10 03:20:02 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.