grouper-users - [grouper-users] RE: GRP-1128: Non-English chars issue
Subject: Grouper Users - Open Discussion List
List archive
- From: Chris Hyzer <>
- To: grouper-users <>
- Subject: [grouper-users] RE: GRP-1128: Non-English chars issue
- Date: Thu, 21 May 2015 16:02:22 +0000
- Accept-language: en-US
There were issues with Grouper and international characters. In this case it had nothing to do with the grouper code, but rather the database settings, connect string, file encoding, and java startup parameters.
In Grouper 2.2.1 patch grouper_v2_2_1_api_patch_9 there are checks at startup to check for non English character handling, database transactions, and database case sensitivity.. There are checks at startup to make sure the non tomcat settings are correct, also the default for grouper.base.properties for file encoding was changed. If you dont need non english chars and you are worried
about the risk of this change please change it in grouper.properties # when reading writing files from util classes, this is encoding (was ISO-8859-1) grouper.default.fileEncoding = UTF-8 These settings will detect if you database and file system can handle utf-8, and if transactions, and case sensitivity are handled correctly. You can get a success message if you are debugging, but this defaults
to off. These will run in another thread so they dont affect start time (optionally default to true) # if should check database and utf in new thread configuration.checkDatabaseAndUtf.inNewThread = true # if grouper should check to see if the database has case sensitive selects configuration.detect.db.caseSensitive.problems = true configuration.display.db.caseSensitive.success.message = false # if grouper should check to see if utf-8 works on startup in files configuration.detect.utf8.file.problems = true # if grouper should check to see if utf-8 works on startup in the database configuration.detect.utf8.problems = true configuration.display.utf8.success.message = false # if grouper in the utf8 check will check to see if grouper supports transaction configuration.detect.db.transaction.problems = true configuration.display.transaction.success.message = false If there is a problem with start, you will see a message like this, but it will not cause grouper not to start: Error: Cannot properly read UTF string from database: '???????', make sure your database has UTF tables and perhaps a hibernate.connection.url in grouper.hibernate.properties Note, it will try to give suggestions about what the problem could be. https://spaces.internet2.edu/display/Grouper/Grouper+internationalization https://bugs.internet2.edu/jira/browse/GRP-1128 https://github.com/Internet2/grouper/commit/cd08054e2b549aa0b5ed45f3215109ae3986936c
https://github.com/Internet2/grouper/commit/fa240bd99306bcec3bca6e3ae68570038baadf42 https://spaces.internet2.edu/display/Grouper/v2.2+Release+Notes Thanks, Chris From: [mailto:]
On Behalf Of Misagh Moayyed Chris, Following up on your suggestion to try out GRP-1128 with the installer, I am not seeing anything different from master. Just ran a 2.2.1 install and tried to create a group as
میثاق Attached is what I see. Misagh |
- [grouper-users] RE: GRP-1128: Non-English chars issue, Chris Hyzer, 05/21/2015
Archive powered by MHonArc 2.6.16.