[
https://issues.apache.org/jira/browse/ISIS-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863026#comment-15863026
]
ASF subversion and git services commented on ISIS-1577:
-------------------------------------------------------
Commit b2b41a971c30b9a5bbc10a03382ee6638a6aed53 in isis's branch
refs/heads/maint-1.14.0 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b2b41a9 ]
ISIS-1577: when populating the command DTO (XML), use the transactionId of the
existing CommandContext if available.
> The transactionId within a command XML does not correspond with the
> transactionId of the command's metadata.
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-1577
> URL: https://issues.apache.org/jira/browse/ISIS-1577
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.13.2.1
> Reporter: Dan Haywood
> Priority: Minor
> Fix For: 1.14.0
>
>
> To reproduce, using Estatio-ECP
> - Invoice > Calculate ... choose OXF-MEDIAX-002
> - Activity > Recent Changes to inspect the command.
> The command and corresponding published event are both persisted and
> associated with the same xactn Id. But the xactn Id of the command's XML is
> different.
> This is probably because there are two xactns for commands.... really, there
> should in the happy case be only one xactn, with a 2nd xactn created if there
> was a probably executing thecommand.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
