[
https://issues.apache.org/jira/browse/SANDESHA2-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Mireaux updated SANDESHA2-138:
---------------------------------------
Description:
ApplicationMsgProcessor.addCreateSequenceMessage insert an RMSBean and then set
two more fields : ReferenceMessageStoreKey and (optionnaly) SecurityTokenData
but don't call update for the RMSBean which works fine with inMemory Storage
but not with Persistent Storage.
Note : unlink the snapshot, the 1.3 release of Sandesha2 was setting the two
field before calling insert.
was:
ApplicationMsgProcessor.addCreateSequenceMessage insert an RMSBean and then set
two more fields : ReferenceMessageStoreKey and (optionnaly) SecurityTokenData
but don't call update for the RMSBean which works fine with inMemory Storage
but not with Persistent Storage.
Note : the 1.3 release of Sandesha2 was setting the two field before the
insert call.
> ApplicationMsgProcessor don't update an RMSBean after modifications
> -------------------------------------------------------------------
>
> Key: SANDESHA2-138
> URL: https://issues.apache.org/jira/browse/SANDESHA2-138
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Francois Mireaux
> Priority: Critical
> Attachments: appmsgproc.patch
>
>
> ApplicationMsgProcessor.addCreateSequenceMessage insert an RMSBean and then
> set two more fields : ReferenceMessageStoreKey and (optionnaly)
> SecurityTokenData but don't call update for the RMSBean which works fine with
> inMemory Storage but not with Persistent Storage.
> Note : unlink the snapshot, the 1.3 release of Sandesha2 was setting the two
> field before calling insert.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
