tirsen / activemessaging

ActiveMessaging is an attempt to bring the simplicity and elegance of Rails development to the world of messaging. Messaging, (or event-driven architecture) is widely used for enterprise integration, with frameworks such as Java's JMS, and products such as ActiveMQ, Tibco, IBM MQSeries etc
0 stars 0 forks source link

getting attributes and manipulating aSQS attributes is broken or difficult #30

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
* calling queue.get_attribute was returning an empty hash when it should have 
been returning 
the approximate number of messages and the visibility timeout
* trying to manipulate the attributes (like manually setting the visibility 
timeout) is not really 
possible because all the methods one needs are protected or private.  NOTE: I 
made some of 
these methods public, even though they don't exist for other queue systems 
(like stomp).  This 
might be a bad design choice?

What is the expected output? What do you see instead?
* for get_attribute, it should return a hash with some values included

What version of the product are you using? On what operating system?
* most recent trunk version

Please provide any additional information below.

Original issue reported on code.google.com by adam.gre...@gmail.com on 5 Jun 2008 at 4:33

Attachments:

GoogleCodeExporter commented 9 years ago
hey,
any chance this could be applied to the main branch?  I'm just hoping to get 
back on the main branch instead of 
having to keep patching activemessaging trunk for my application ;)

thanks,
Adam

Original comment by adam.gre...@gmail.com on 17 Jul 2008 at 5:01

GoogleCodeExporter commented 9 years ago
I'm a bit torn on this as I have not to date allowed additions to adapters that 
were
not common across the different brokers. I need to think about this one a bit...

The purest in my doesn't like it, but the pragmatic sees it as really just an
eventuality - brokers are so different.  So with that said, I need to think 
about how
best to represent such methods so it is clear they are broker specific - 
perhaps a
naming convention ... or a helper object that is broker specific ... something.

Original comment by kooks...@gmail.com on 17 Jul 2008 at 5:12