[
https://issues.apache.org/activemq/browse/AMQ-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56996#action_56996
]
Steve Halverson commented on AMQ-1377:
--------------------------------------
Arjan,
I created an example that successfully used the prototype adapter. I then
tried to use your new dojo adapter but did not have much success. Whenever I
add a listener it does the POST operation but the polling terminates shortly
after. The current poll finishes; but a new one does not start. It seems that
the dojo.xhrGet does not get a chance to do its callback to keep the polling
alive. Did you have any issues with your dojo adapter?
> amq.js should not have a dependency on prototype.js
> ---------------------------------------------------
>
> Key: AMQ-1377
> URL: https://issues.apache.org/activemq/browse/AMQ-1377
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.0.0
> Reporter: Jim Cook
> Fix For: 5.4.0
>
> Attachments: amq.js, amq.js, amq.js, amq_dojo_adapter.js, amq_js.zip
>
>
> amq.js uses a script loading technique to include behavior.js, prototype.js
> and _amq.js. The Behavior library is included only for the purposes of the
> chat client and is only GUI in nature, so that should go. Also, Prototype is
> included for its AJAX functionality, however everyone has their favorite
> javascript library and although I cut my teeth on prototype, I use jQuery
> now. I certainly don't want amq.js to include prototype when I have a
> perfectly good AJAX library already included in jQuery.
> IMHO, amq.js should include only the functionality of client-side
> javascript-enabled JMS. The page author should include her AJAX library of
> choice (prototype, dojo, jquery, mootools, etc.) and an adapter class that
> allows amq.js to use the particular ajax library.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
