Bug 833345
| Summary: | Designer does not work with Unicode package names | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Zuzana Krejčová <zkrejcov> | ||||
| Component: | BRM (Guvnor), jBPM Console | Assignee: | manstis | ||||
| Status: | MODIFIED --- | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | kverlaen | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Including unicode characters in package names stops the process designer from being able to load the packages. As such, when creating new processes it is important not to include unicode characters in either the process name or the process ID, as this is not currently supported and will result in unexpected behavior from the process designer.
|
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: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Zuzana Krejčová
2012-06-19 09:24:05 UTC
Done in Designer 2.3.x branch. Sorry but still happening. (i) in Designer says the Designer version is 2.2.1.Final. Was the fix picked for that version too? It has not. Seems the build did not pick up the right Designer version? Tried once more with the current build, Designer version 2.3.1-DEV, used "žlýOškliváPakážů" as a package name. It looks like part of the issue was fixed, but there are still problems. I can now see the process information in the left panel, process package, ID and name are set and show correctly. The minimal perspective though still shows shapes without their categories - that makes quite a mess in it. Process can be validated without the "Invalid answer from server." message. I can't get a .png for the process, server log says: WARNING [JAXRSInInterceptor] No root resource matching request path /jboss-brms/rest/packages/%C5%BEl%C3%BDO%C5%A1kliv%C3%A1Pak%C3%A1%C5%BE%C5%AF/assets/þlýOákliváPakáþï.testProcess-image has been found, Relative Path: /packages/%C5%BEl%C3%BDO%C5%A1kliv%C3%A1Pak%C3%A1%C5%BE%C5%AF/assets/þlýOákliváPakáþï.testProcess-image. Please enable FINE/TRACE log level for more details. Creating the process in the package in the first place resulted in: ERROR [RulesRepository] Unable to load a rule package. javax.jcr.PathNotFoundException: žlýOÅ¡kliváPakážů at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2135) though I could work on the process after the Designer loaded. Yes, this is an issue with Designer using the REST api of Guvnor which currently cannot handle new files added via it that include unicode characters. In this case we need to document that even tho the users asset has unicode characters in it, that the process ID and the process name should NOT include unicode characters. This will solve the above issue. Thanks. Lee, could you please add it to our docs (comment 6)? (CC Lee) Sure, Zuzana. Tiho, would adding the follow text/section to the process designer chapter cover the situation? And if so, is this issue present in the community as well? I can submit a pull request if it is. *Process Designer and Unicode Characters* When creating new processes it is important not to include unicode characters in either the process name or the process ID, as this is not currently supported and will result in unexpected behavior from the process designer. Thanks Lee Hi Lee, I would write: "....and will result in unexpected behavior from the process designer." -> "...and will result in unexpected behavior when saving and retrieving your process assets". WDYT? Thanks Tiho, I've added a note that states: When creating new processes it is important not to include unicode characters in either the process name or the process ID, as this is not currently supported and will result in unexpected behavior from the process designer when saving and retrieving the process assets. I'll post a link to the doc stage as soon as the content has been uploaded. Thanks Lee Setting the release flag to - as this issue did not make it into the release. Documentation was done. Release notes text updated (see doc_text field) - the issue will be filed as a known issue in the release notes. Release notes text updated (see doc_text field) - the issue will be filed as a known issue in the release notes. |