You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (Updated) (JIRA)" <ji...@apache.org> on 2011/10/27 22:30:32 UTC
[jira] [Updated] (CXF-3853) RMTxStore: Vendor specific condition
check
[ https://issues.apache.org/jira/browse/CXF-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-3853:
-----------------------------
Fix Version/s: 2.3.8
> RMTxStore: Vendor specific condition check
> ------------------------------------------
>
> Key: CXF-3853
> URL: https://issues.apache.org/jira/browse/CXF-3853
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Reporter: Harsha Hegde
> Assignee: Aki Yoshida
> Fix For: 2.3.8, 2.4.4, 2.5
>
>
> While using the reliable messaging in the CXF. The condition checks to create Database tables for a given RM store is vendor specific. As the method which does this check is private static, this behavior cannot be overridden.
> In the class org.apache.cxf.ws.rm.persistence.jdbc.RMTxStore the while initializing the RM store the method isTableExistsError is hard coded with vendor error codes for derby and oracle, so if we use any other RDBMS underneath then we run into errors that the tables already exists. As this method is private static this cannot be overridden either.
> Please provide means to have vendor independent checks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira