[
https://issues.jboss.org/browse/GTNPORTAL-2739?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration commented on GTNPORTAL-2739:
----------------------------------------------------
Viliam Rockai <vrockai(a)redhat.com> made a comment on [bug
879670|https://bugzilla.redhat.com/show_bug.cgi?id=879670]
The problem is in the datasouce configuration. You are disabling the JTA (setting
jta=false), but the default value in gatein/jpp is jta=true. Deleting jta=false from the
datasouce configuration (true is the default value) resolves this problem.
Add db-tablename-suffix property to JCR configuration to make it
Oracle ready
-----------------------------------------------------------------------------
Key: GTNPORTAL-2739
URL:
https://issues.jboss.org/browse/GTNPORTAL-2739
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.5.0.Beta02
Reporter: Viliam Rockai
Assignee: Viliam Rockai
Fix For: 3.5.0.Final
Add db-tablename-suffix property to JCR configuration to make it Oracle ready. Due to max
identificator length, GateIn does not work correctly in isolated mode with Oracle. Using
the db-tablename-suffix property in JCR configuration, this can be easily fixed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira