activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <>
Subject [jira] Resolved: (AMQ-1377) amq.js should not have a dependency on prototype.js
Date Mon, 19 Apr 2010 15:36:16 GMT


Dejan Bosanac resolved AMQ-1377.

    Resolution: Fixed

I finally integrated this with the trunk (svn revision 935623). Sorry for taking so long.
I included all adapters found here and updated libs to the newest stable releases. So, now
all we need to do is properly document it and continue contributing to it. Thanks all for
great work.

BTW. You may be interested in web socket support as well

> amq.js should not have a dependency on prototype.js
> ---------------------------------------------------
>                 Key: AMQ-1377
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.0.0
>            Reporter: Jim Cook
>            Assignee: Dejan Bosanac
>             Fix For: 5.4.0
>         Attachments: amq.js, amq.js, amq.js, amq_dojo_adapter.js,
> 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.

View raw message