[TORQUE-1090] TorqueBox.fetch uses javax.jms.Destination implementation instead of queue name in the TorqueBox::Messaging::Queue constructor #161

Merged
merged 1 commit into from May 9, 2013

Conversation

Projects
None yet
2 participants
Owner

goldmann commented May 9, 2013

Fixes the issue where TorqueBox.fetch sends wrong object as the first
argument of the constructor in TorqueBox::Messaging::Queue (and Topic)
class. It was an implementation of javax.jms.Destination interface, but
should be a simple String.

The TorqueBox Project » torquebox #137 FAILURE
Looks like there's a problem with this pull request
(what's this?)

@goldmann goldmann [TORQUE-1090] Improper assigning of the name instance variable in Tor…
…queBox::Messaging::Queue and Topic when using the javax.jms.Destination as the destination

Fixes the issue where TorqueBox.fetch sends javax.jms.Destination object
as the first argument of the constructor in TorqueBox::Messaging::Queue
(and Topic) class. The TorqueBox::Messaging::Queue class stores
thisobject in @java_destination instance variable instead of messing the @name
variable.
6843029

@goldmann goldmann merged commit 6843029 into torquebox:master May 9, 2013

The TorqueBox Project » torquebox #138 FAILURE
Looks like there's a problem with this pull request
(what's this?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment