The participant used for testing the @LRA annotation defined at the class level only defines LRA.Type.SUPPORTS for the Type attribute:
@Path(LraResource.LRA_RESOURCE_PATH)
@LRA(value = LRA.Type.SUPPORTS, end = false)
public class LraResource extends ResourceParent
...
So, for example, if there is no incoming LRA context then the expected behaviour around starting LRAs is not validated.
We should add TCK tests that verify the correct behaviour with other values of the LRA.Type element (https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/ws/rs/LRA.java#L166).
As well as the extra tests the specification text that describes @LRA annotation behaviour defined at the class level should be enhanced.
The participant used for testing the @LRA annotation defined at the class level only defines LRA.Type.SUPPORTS for the Type attribute:
So, for example, if there is no incoming LRA context then the expected behaviour around starting LRAs is not validated.
We should add TCK tests that verify the correct behaviour with other values of the LRA.Type element (https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/ws/rs/LRA.java#L166).
As well as the extra tests the specification text that describes @LRA annotation behaviour defined at the class level should be enhanced.