Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 614683 - Drain and Spout should use only standard JMS methods
Drain and Spout should use only standard JMS methods
Status: CLOSED WONTFIX
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java (Show other bugs)
Development
All Linux
low Severity low
: 1.3
: ---
Assigned To: Rajith Attapattu
MRG Quality Engineering
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-14 20:51 EDT by Rajith Attapattu
Modified: 2010-07-20 19:11 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-20 19:11:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rajith Attapattu 2010-07-14 20:51:31 EDT
Description of problem:
The Drain and Spout examples used in qpid-java-examples rpm contains non JMS classes for creating destinations.
Ex 

Insted of doing,

 Destination dest = new AMQAnyDestination(address);

the following is better,

 Destination dest = new session.createQueue(address);

Version-Release number of selected component (if applicable):


How reproducible:
N/A

Steps to Reproduce:
N/A
  
Actual results:
N/A

Expected results:
N/A

Additional info:
Comment 1 Rajith Attapattu 2010-07-20 19:11:41 EDT
Drain and Spout are not meant to be code examples, rather utilities that can be used to learn and understand the addressing syntax.

It is actually semantically incorrect to use session.createQueue instead of AMQAnyDestination when you actually want to use it for a topic.

Therefore it's best to leave the Drain and Spout examples as it is and mention explicitly in the documentation that drain and spout are not code examples.

We need to provide a proper application that can be used as a code example in all the client languages and then use that as a basis when explaining code segments in the documentation.

Note You need to log in before you can comment on or make changes to this bug.