Thank you :) I managed to solve the problem by inspecting the object message
;)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Porblem-extracting-XML-data-in-Firefox-with-ActiveMQ-Ajax-client-tp3220032p3224749.html
Sent from the ActiveMQ - User mailing list archive at Nab
On Jan 17, 2011, at 9:28 AM, Alex Dean wrote:
>
> 2. In your callback function, I believe message.nodeValue will be available
> in either browser, and will be a string containing the message sent by the
> server.
I looked at this a little more, and nodeValue can have different contents
depen
1. You have jquery available, which can make a lot of
'document.getElementById()' & other lower-level JavaScript unnecessary. jQuery
is also pretty good at smoothing out the differences between JS implementations
in different browsers.
2. In your callback function, I believe message.nodeValue
Any idea about this?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Porblem-extracting-XML-data-in-Firefox-with-ActiveMQ-Ajax-client-tp3220032p3220940.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
