[
https://issues.apache.org/jira/browse/CXF-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748475#action_12748475
]
Dan Ryazansky commented on CXF-2407:
------------------------------------
The following changes were made in RMTxStore.java:
from
"CUR_MSG_NO DECIMAL(31, 0) NOT NULL DEFAULT 1, "
to
"CUR_MSG_NO DECIMAL(31, 0) DEFAULT 1 NOT NULL, "
Derby doesn't care about the order of NOT NULL / DEFAULT, Oracle does
from
"EXPIRY BIGINT, "
to
"EXPIRY DECIMAL(31, 0), "
Oracle doesn't have BIGINT. DECIMAL is the one data type that seems to work
across different DBs.
from
"X0Y32".equals(ex.getSQLState())
to
"X0Y32".equals(ex.getSQLState()) || 955 == ex.getErrorCode() When checking for
table creation (955 is the Oracle error code if the table already exists).
> WS-RM Connecting to Oracle
> --------------------------
>
> Key: CXF-2407
> URL: https://issues.apache.org/jira/browse/CXF-2407
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Affects Versions: 2.2.3
> Reporter: Dan Ryazansky
>
> The current version of CXF uses a Derby database when Reliable messaging is
> turned on. Make ORACLE an option to connect to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
