Bug 696746
Summary: | Qpid JCA Adapter Integration With Alternate Application Servers | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Weston M. Price <wprice> | ||||
Component: | qpid-jca | Assignee: | messaging-bugs <messaging-bugs> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | MRG Quality Engineering <mrgqe-bugs> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | Development | CC: | astitcher, cdewolf, freznice, iboverma, tross | ||||
Target Milestone: | 2.0.4 | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | qpid-java-jca-0.10-4 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-11-22 14:14: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: | |||||||
Attachments: |
|
*** This bug has been marked as a duplicate of bug 700494 *** |
Created attachment 492200 [details] Patch for the aformentioned issue. Description of problem: As reported from the field: Currently the QpidDestinationProxy class that is responsible for allowing JMS destinations to be bound into a JNDI tree for use does not work in alternate application servers being that the QpidDestinationProxy is being returned directly, rather than the Referenceable objects that it produces. As a result, on alternate platforms, ClassCastExceptions resulted threby rendering the adapter unusable in non JBoss environments. Version-Release number of selected component (if applicable): Current development version of the Qpid JCA adapter Steps to Reproduce: 1.Deploy the adapter and run any application code in alternate application server. Actual results: ClassCastExceptions as expected objects do not correctly implement required interfaces. Additional info: Again, this has been reported in the field and as such the patch was provided by our consulting arm with a few minor modifications. I have attached a patch that fixes the issue. This work will also be integrated by the JCA team via standard SCM channels