[JBoss JIRA] (JBTM-3125) Some LRA&RTS tests uses wrong String.format parameters
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3125?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated JBTM-3125:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Some LRA&RTS tests uses wrong String.format parameters
> ------------------------------------------------------
>
> Key: JBTM-3125
> URL: https://issues.jboss.org/browse/JBTM-3125
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA, REST
> Affects Versions: 5.9.3.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Optional
>
> Some tests uses wrong {{String.format}}. For example wrong number of arguments for the {{format}} methdo
> {code}
> System.out.printf("SRA: %s: Updating hotel participant state to: ", bookingId, status);
> {code}
> should be
> {code}
> System.out.printf("SRA: %s: Updating hotel participant state to: %s", bookingId, status);
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-3058) Add STM tests that verify nested transactions are closed
by Michael Musgrove (Jira)
[ https://issues.jboss.org/browse/JBTM-3058?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-3058:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Add STM tests that verify nested transactions are closed
> --------------------------------------------------------
>
> Key: JBTM-3058
> URL: https://issues.jboss.org/browse/JBTM-3058
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: STM, Testing
> Affects Versions: 5.9.0.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Optional
> Fix For: 5.next
>
>
> STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions follow the closed model.
> Furthermore, STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model.
> Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "[Tips on how to evaluate STM implementations|http://example.com|https://jbossts.blogspot.com/2018/09/t...]"
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated JBTM-3123:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> LRA POST to "start" has Incorrect @ApiResponse annotation
> ---------------------------------------------------------
>
> Key: JBTM-3123
> URL: https://issues.jboss.org/browse/JBTM-3123
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: LRA
> Affects Versions: 5.9.3.Final
> Reporter: Lance Ball
> Assignee: Martin Stefanko
> Priority: Minor
>
> In {{java.io.narayana.lra.coordinator.api.Coordinator}} the {{@ApiResponse}} annotation [specifies a response code |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L227] of {{200}} for the "start" endpoint, however, [what is actually returned |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L281] is {{Response.Status.CREATED}} which is HTTP code {{201}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka commented on JBTM-3123:
---------------------------------------
[~lanceball] the swagger annotation was changed to reflect the operation. Thanks [~mstefank] for the fix and thanks [~lanceball] for the report.
> LRA POST to "start" has Incorrect @ApiResponse annotation
> ---------------------------------------------------------
>
> Key: JBTM-3123
> URL: https://issues.jboss.org/browse/JBTM-3123
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: LRA
> Affects Versions: 5.9.3.Final
> Reporter: Lance Ball
> Assignee: Martin Stefanko
> Priority: Minor
>
> In {{java.io.narayana.lra.coordinator.api.Coordinator}} the {{@ApiResponse}} annotation [specifies a response code |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L227] of {{200}} for the "start" endpoint, however, [what is actually returned |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L281] is {{Response.Status.CREATED}} which is HTTP code {{201}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated JBTM-3123:
----------------------------------
Git Pull Request: https://github.com/jbosstm/narayana/pull/1426
> LRA POST to "start" has Incorrect @ApiResponse annotation
> ---------------------------------------------------------
>
> Key: JBTM-3123
> URL: https://issues.jboss.org/browse/JBTM-3123
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: LRA
> Affects Versions: 5.9.3.Final
> Reporter: Lance Ball
> Assignee: Martin Stefanko
> Priority: Minor
>
> In {{java.io.narayana.lra.coordinator.api.Coordinator}} the {{@ApiResponse}} annotation [specifies a response code |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L227] of {{200}} for the "start" endpoint, however, [what is actually returned |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L281] is {{Response.Status.CREATED}} which is HTTP code {{201}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-3125) Some LRA&RTS tests uses wrong String.format parameters
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3125?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated JBTM-3125:
----------------------------------
Summary: Some LRA&RTS tests uses wrong String.format parameters (was: Some LRA&RTS tests uses wrong String.format paramters)
> Some LRA&RTS tests uses wrong String.format parameters
> ------------------------------------------------------
>
> Key: JBTM-3125
> URL: https://issues.jboss.org/browse/JBTM-3125
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA, REST
> Affects Versions: 5.9.3.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Optional
>
> Some tests uses wrong {{String.format}}. For example wrong number of arguments for the {{format}} methdo
> {code}
> System.out.printf("SRA: %s: Updating hotel participant state to: ", bookingId, status);
> {code}
> should be
> {code}
> System.out.printf("SRA: %s: Updating hotel participant state to: %s", bookingId, status);
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-3125) Some LRA&RTS tests uses wrong String.format paramters
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3125?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Ondra Chaloupka created pull request #1427 in GitHub
----------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> Some LRA&RTS tests uses wrong String.format paramters
> -----------------------------------------------------
>
> Key: JBTM-3125
> URL: https://issues.jboss.org/browse/JBTM-3125
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA, REST
> Affects Versions: 5.9.3.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Optional
>
> Some tests uses wrong {{String.format}}. For example wrong number of arguments for the {{format}} methdo
> {code}
> System.out.printf("SRA: %s: Updating hotel participant state to: ", bookingId, status);
> {code}
> should be
> {code}
> System.out.printf("SRA: %s: Updating hotel participant state to: %s", bookingId, status);
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months