using JMSQueueService to create and bind queues to new contexts with
previously-non-existant-parents causes MockContext/BindingTrap/HornetQ to get confused on
context heritage
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-830
URL:
https://issues.jboss.org/browse/AS7-830
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Reporter: Bob McWhirter
Assignee: Jason Greene
If I hijack JMSQueueService, and attempt to bind the queue as
queue/foo/bar/baz/tacos/someQueue, it may work the first time, but subsequent created
queues end up with a duplicated section in the resulting path. Trying to bind to
queue/foo/bar/baz/gouda/anotherQueue might result in
queue/foo/bar/baz/tacos/gouda/anotherQueue.
Seems some stack doesn't get completely popped when HornetQ goes creating parent
contexts in order to plant the leaf resource.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira