cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eoghan Glynn <eogl...@gmail.com>
Subject Re: Reliable messaging: Connecting to Oracle
Date Mon, 31 Aug 2009 20:48:22 GMT
Thanks for the patch, Dan. Your efforts are much appreciated.

I've committed the fix just now in r809738.

Cheers,
Eoghan

2009/8/27 Daniel Kulp <dkulp@apache.org>

>
> Please file a JIRA and submit the changes as a patch.   This is excellent!
>
> https://issues.apache.org/jira/browse/CXF
>
>
> Dan
>
> On Thu August 27 2009 10:17:52 am Dan Ryazansky wrote:
> > The current version of CXF uses a Derby database when Reliable messaging
> is
> > turned on. However, we required use of ORACLE.
> >
> > I had to make the following changes to to make the code database agnostic
> > in RMTxStore:
> >
> > 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).
> >
> > Is this something that should be committed into the repository?
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message