[jira] Updated: (AMQ-1377) amq.js should not have a dependency on prototype.js

["Arjan van den Berg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arjan van den Berg updated AMQ-1377:
------------------------------------

    Attachment: amq_dojo_adapter.js

This file contains an adapter to use amq.js with the Dojo javascript library (http://www.dojotoolkit.org/).
Probably some refactoring or more comments are needed.

> 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.