Bug 767215 - use of session.createReceiver() not consistent with rest of jbpm-human-task code
Summary: use of session.createReceiver() not consistent with rest of jbpm-human-task code
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Kris Verlaenen
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-13 14:54 UTC by Jeffrey Bride
Modified: 2020-04-27 01:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jeffrey Bride 2011-12-13 14:54:02 UTC 
the use of session.createReceiver() in line 98 of org.jbpm.task.service.jms.BaseJMSTaskServer.java

is inconsistent with the use of session.createQueue() everywhere else in the jbpm-human-task functionality.

one side-affect of this is that the use of createReceiver() on a qpid JMS session does *NOT* auto-create the jbpm human-task queue if it does not already exist.  This behavior is inconsistent with the auto-creation of queues with the client-side human-task queue when using Qpid as well as both client & server side queues when using Hornetq.

thanks, jeff
Comment 1 Kris Verlaenen 2012-01-27 15:06:46 UTC 
Fixed in community, should be available in next build.
Comment 3 Lukáš Petrovický 2012-05-21 07:29:23 UTC 
Verified in source code. ER7.
Note You need to log in before you can comment on or make changes to this bug.