[ http://jira.jboss.com/jira/browse/JBMESSAGING-480?page=all ] Tim Fox updated JBMESSAGING-480: -------------------------------- Description: The current partial solution to the super task assumes that a Delivery is returned with "selectorAccepted=false" when a receiver does not want to accept a message. This is ambiguous and is not part of the Receiver's public contract. Since a Receiver could also return null if the selector didn't match, We need to clarify the behaviour and change the contract of a Receiver to make all these cases explicit. I would recommend changing the return value of handle so that we can distinguish between the message not being accepted due to the receiver being closed, full or not matching a selector -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-480?page=all ] Ovidiu Feodorov updated JBMESSAGING-480: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-480?page=all ] Tim Fox closed JBMESSAGING-480. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira