activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saira Gul (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1377) amq.js should not have a dependency on prototype.js
Date Wed, 16 Jul 2008 07:13:00 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44321#action_44321
] 

Saira Gul commented on AMQ-1377:
--------------------------------

hi Dan!!

I have added your's modified amq.js files in my application, its work quite fine. Thanks.

I want to know one thing is there any impact of pooling on activeMQ performance? Actually
ActiveMQ got disconnected after giving the following exception at  console

"Could not accept connection : Channel was inactive for too long"

and also i got this exception in application log:

 "Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException:
Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException:
Connection refused; nested exception is java.net.ConnectException: Connection refused"

I wonder due to pooling ActiveMQ becomes slower than Ajax client, is it true or my misconception?

Thanks

> 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
>         Attachments: amq.js, amq.js, amq.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.


Mime
View raw message