[jira] [Commented] (CXF-6646) CXF 3.x WSRM message may not be retrieved from database

["Akitoshi Yoshida (JIRA)" <ji...@apache.org>]

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

Akitoshi Yoshida commented on CXF-6646:
---------------------------------------

While looking at the change introduced with CXF-4866, it seems to require a more drastic change to fix the issue.

The patch currently attached to this ticket preserves the content in some cases but it uses a complex sequence of operations and it also does not cover for the attachments.

If we are to stay in the current model, one option will be to go back to use CachedOutputStream in
RMMessage and serialize the whole message including the attachments in
one blob associated with this content. In that way, the DB operation
is kept simpler (one table write) when storing a multipart message and
it also keeps the management of attachment resources simpler (no need
to cache the attachment streams separately).





> CXF 3.x WSRM message may not be retrieved from database
> -------------------------------------------------------
>
>                 Key: CXF-6646
>                 URL: https://issues.apache.org/jira/browse/CXF-6646
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 3.0.4
>            Reporter: Kai Rommel
>            Assignee: Akitoshi Yoshida
>         Attachments: 0001-WSRM-enable-RMTxStore-for-different-database-impleme.patch, 0002-WSRM-enable-RMTxStore-for-different-database-impleme.patch
>
>
> With CXF-4866, CXF-352 changes to the RMTxStore implementation were introduced.
> Running the JUnit Tests for rt/ws/rm with a newer Derby version, some tests will fail.
> You can switch to version 10.8.2.2 and messages won't be recovered from database, as database connection will be released before message is read.
> I used the CachedOutputStream to cache the message. Find attached the patch files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)