[
https://issues.apache.org/jira/browse/PROTON-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867221#comment-13867221
]
Rafael H. Schloming commented on PROTON-484:
--------------------------------------------
I've pasted an excerpt from the spec below. I believe the way it describes the
default-outcome suggests that it should apply in this situation. I've also
pasted the definition of the outcomes field which implies that you should
assume a default outcome of ACCEPTED in this case. I can provide a workaround,
but strictly speaking I think the broker should be able to handle this
situation.
<field name="default-outcome" type="*" requires="outcome"
label="default outcome for unsettled transfers">
<doc>
<p>
Indicates the outcome to be used for transfers that have not
reached a terminal state at
the receiver when the transfer is settled, including when the
source is destroyed. The
value MUST be a valid outcome (e.g., <xref name="released"/> or
<xref name="rejected"/>).
</p>
</doc>
</field>
<field name="outcomes" type="symbol" multiple="true"
label="descriptors for the outcomes that can be chosen on this
link">
<doc>
<p>
The values in this field are the symbolic descriptors of the
outcomes that can be chosen
on this link. This field MAY be empty, indicating that the
<i>default-outcome</i> will
be assumed for all message transfers (if the default-outcome is not
set, and no outcomes
are provided, then the <xref name="accepted"/> outcome MUST be
supported by the source).
</p>
<p>
When present, the values MUST be a symbolic descriptor of a valid
outcome, e.g.,
"amqp:accepted:list".
</p>
</doc>
</field>
> Disposition Frane: Missing DeliveryState, no default outcome
> ------------------------------------------------------------
>
> Key: PROTON-484
> URL: https://issues.apache.org/jira/browse/PROTON-484
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.5
> Reporter: Andreas Mueller
>
> If a message is delivered from a broker to Proton-C by a transfer frame with
> settled=false, Proton sends a disposition frame with settled=true but without
> a delivery state. A delivery state is required because a message can be e.g.
> accepted or rejected through a disposition frame.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
