Bug 700500

Summary: Support "standalone" JMS clients for QE JCA testing
Product: Red Hat Enterprise MRG Reporter: Weston M. Price <wprice>
Component: qpid-jcaAssignee: Andrew Stitcher <astitcher>
Status: CLOSED CURRENTRELEASE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: DevelopmentCC: astitcher, cdewolf, iboverma, jpechane, mnovak, pslavice, tross
Target Milestone: 2.1.2   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Weston M. Price 2011-04-28 14:36:53 UTC
Description of problem:
As part of our QE/QA testing for JCA, 'thin' client scenarios are required to properly support QE's goal of replacing the default messaging provider with QPID. While a majority of the testing scenarios can be accomplished within the context of the application server, a few test cases require the use of the JCA adapter outside of the JBoss environment. This will involve two steps:

1) Configure the adapter to provide the required jars that can be consumed by 'thin' client testing scenarios. Currently, the QPID JCA adapter is self contained and does export/expose it's jars outside of the adapter proper.

2)Rigorous testing in terms of serialization with the test client as this is required.


Version-Release number of selected component (if applicable):
Current development version of the adapter

How reproducible:
NA

Steps to Reproduce:
NA  

Actual results:
Allow for 'thin' client use of the QPID JCA adapter outside of the app server.

Expected results:
Comply with QE's testing scenarios/plan

Additional info:
This essentially amounts to taking the work that has currently been done with the TCK and integrating that into QE's test harness/plans.

Comment 2 Pavel Slavicek 2011-06-24 12:05:46 UTC
Hi Andrew, could you provide link to the official/actual source code, please?

Comment 4 Weston M. Price 2011-09-18 05:23:41 UTC
This behavior is included in the adapter as well as the examples.

Comment 5 Andrew Stitcher 2011-09-22 13:30:23 UTC
This has been fixed in package qpid-java-jca-0.10-10