[
https://issues.apache.org/jira/browse/BOOKKEEPER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414948#comment-13414948
]
Mridul Muralidharan commented on BOOKKEEPER-310:
------------------------------------------------
The testcases you mention are already present under activemq's testcases under
jms provider : I think I already specified this earlier.
The caveat is that it wont work in a clustered deployment due to changes in
seq-id in remote server (if I understood it right) - the jms testcase does not
depend on this.
I am not sure what codepaths this testcase tests (or is extended to test), but
did not want to make changes which will limit its usability.
If that is not the case, we can add some rudimentary checks on the seq-id.
> Changes in hedwig server to support JMS spec
> --------------------------------------------
>
> Key: BOOKKEEPER-310
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-310
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Mridul Muralidharan
> Attachments: hedwig-server.patch, hedwig-server.patch.1,
> hedwig-server.patch.3, hedwig-server.patch.4
>
>
> The primary changes are :
> a) Support modified protocol changes (optional body).
> b) Return the published message's seq-id in the response.
> c) Minor bugfix to Array indexing in bucket which was triggered in a testcase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
