You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am sorry Rudy, on the gitter room when I said I agreed I thought you were talking about the opaque user data on callbacks but when I checked the spec I see that we deferred #15 to milestone 2.
In issue #105 we agreed on URI so I think all we need to do is change all of our examples to use a URI for the header. Note also that JAX-RS header parameters can be of any data type.
Also I don't think the goal should be to exactly mimic what the corresponding JAX-RS methods are doing.
Also I don't think the goal should be to exactly mimic what the corresponding JAX-RS methods are doing.
I know, but it makes the implementation easier in this case. Since Payara will always use the Proxy approach, since there will be no REST communication between Participant and 'coordinator', the allowed parameter types of the method will be different depending on the fact if there is a JAX-RS method (like @put) defined or not.
Through Issue #35 (PR #148) the only allowed parameter type on the Complete and Compensate Methods is
java/net.URI
However, in the JAX-RS version, the most common parameter types will be String.
In order to make the spec more uniform, String should also be allowed as parameter types for Complete and Compensate Methods in the non JAX-RS case.
The text was updated successfully, but these errors were encountered: