Bug 614683

Summary: Drain and Spout should use only standard JMS methods
Product: Red Hat Enterprise MRG Reporter: Rajith Attapattu <rattapat+nobody>
Component: qpid-javaAssignee: Rajith Attapattu <rattapat+nobody>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: Development   
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-20 23:11:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rajith Attapattu 2010-07-15 00:51:31 UTC 
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 23:11:41 UTC 
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.