cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Siano (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-3845) Incompatibility between Derby 10.8 and WS-RM RMTxStore
Date Tue, 04 Oct 2011 15:22:34 GMT

    [ https://issues.apache.org/jira/browse/CXF-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120210#comment-13120210
] 

Stephan Siano commented on CXF-3845:
------------------------------------

The change in the RMTxStore is compatible (the old code relies on a bug that booleans are
mapped to "1" and "0" instead of "true" and "false" if mapped to a char, the new coding does
that conversion to "1" and "0" in code, so it behaves as before). 

I can't figure how the same code built against 10.8 should not work with previous versions
(but after changing the version in the parent pom other developers might use API extensions
that are not in 10.2 in future which might then break compatibility).
                
> Incompatibility between Derby 10.8 and WS-RM RMTxStore
> ------------------------------------------------------
>
>                 Key: CXF-3845
>                 URL: https://issues.apache.org/jira/browse/CXF-3845
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.5
>            Reporter: Stephan Siano
>            Priority: Minor
>         Attachments: Update-to-Derby-10812.patch
>
>
> The RMTxStore implementation does not work with Derby versions 10.8 and higher due to
a bugfix for 
> https://issues.apache.org/jira/browse/DERBY-4965. The issue can be reproduced by replacing
the Derby version in the parent pom.xml to 10.8.1.2, afterwards some of the existing test
cases for WS-RM fail.
> The fix for this is rather trivial (and proposed in the Derby 10.8 release notes). I
attach a patch for the trunk to this issue.

--
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

        

Mime
View raw message