Bug 1122342

Summary: Once designer in business-central saves bpmn2 file which uses I18n for a process name, those characters are garbled
Product: [Retired] JBoss BPMS Platform 6 Reporter: Hisao Furuichi <hfuruich>
Component: jBPM DesignerAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED EOL QA Contact: Marek Baluch <mbaluch>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.2CC: bpms-support, kverlaen
Target Milestone: ER2   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:06:19 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 Hisao Furuichi 2014-07-23 03:28:26 UTC
Description of problem:
Once designer in business-central saves bpmn2 file which uses I18n for a process name, those characters are garbled

Steps to Reproduce:
1: Start bpms
2: Create a business process whose process name is Japanese (ex: 日本語)
3: Save process
4: Shutdown bpms
5: Start bpms
6: Open the business process by designer

Actual results:
process name is garbled.

Expected results:
process name is displayed correctly.

Comment 1 Jeremy Lindop 2014-09-26 08:50:00 UTC
https://github.com/droolsjbpm/jbpm-designer/commit/ff130a4dcfdc3137b72d7472a07e500a7cce0dc5

Fixed by base64 encoding/decoding the bpmn json as it is passed from the client to the backend.

Comment 2 Jeremy Lindop 2014-10-02 14:14:11 UTC
Additional fix to create valid BPMN id from the name entered by the user when BP's are initially created. Characters in the name which are invalid in id's are converted to their hex equivalent in the ID.

https://github.com/droolsjbpm/jbpm-designer/commit/86212c2dc4d95b354def7759309e74b29335e3b6

Comment 3 Marek Baluch 2014-12-01 11:54:11 UTC
Verified on 6.1.0.ER2.

Japanese process name is now displayed correctly even after server restart.