[JBoss JIRA] (GTNPORTAL-2368) IDM and JCR in a single database
by tom sebastian (JIRA)
tom sebastian created GTNPORTAL-2368:
----------------------------------------
Summary: IDM and JCR in a single database
Key: GTNPORTAL-2368
URL: https://issues.jboss.org/browse/GTNPORTAL-2368
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Identity integration, JCR integration
Affects Versions: 3.1.0-GA
Environment: GateIn-3.1.0-GA with oracle10g enterprise edition
Reporter: tom sebastian
Assignee: Boleslaw Dawidowicz
Fix For: 3.1.0-GA
hi all,
We are using oracle10g enterprise database instead of hsqldb for JCR,IDM data in GateIn-3.1.0-GA.
Currently we are using 2 seperate oracle databases(SIDs) for JCR and IDM storage.
Can we use a single SID/database for both JCR and IDM data instead of seperate databases.
Please help.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-2337) I18N locale identifier parsing code does not support all valid cases in Java 7
by Chris Laprun (JIRA)
Chris Laprun created GTNPORTAL-2337:
---------------------------------------
Summary: I18N locale identifier parsing code does not support all valid cases in Java 7
Key: GTNPORTAL-2337
URL: https://issues.jboss.org/browse/GTNPORTAL-2337
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Internationalization and Localization
Affects Versions: 3.2.0-Beta01
Reporter: Chris Laprun
According to the Locale Java 7 javadoc:
Java has used ja_JP_JP to represent Japanese as used in Japan together with the Japanese Imperial calendar. This is now representable using a Unicode locale extension, by specifying the Unicode locale key ca (for "calendar") and type japanese. When the Locale constructor is called with the arguments "ja", "JP", "JP", the extension "u-ca-japanese" is automatically added.
This results in a ja_JP_JP_#u-ca-japanese Locale which is currently parsed as invalid. Note that there is a similar issue for Thai.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months