| Summary: | JCA installation, RPM name | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | ppecka <ppecka> |
| Component: | Messaging_Programming_Reference | Assignee: | Joshua Wulf <jwulf> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | chetan, dryan, iboverma, jwulf, lcarlon, wprice |
| Target Milestone: | 2.2 | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-09-20 03:13:35 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
ppecka
2011-12-01 10:18:44 UTC
Hi ppecka, I've added this paragraph in Chapter 1 - Introduction: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html/Qpid_JCA_Adapter_User_Guide/chap-Qpid_JCA_Adapter_User_Guide-Introduction.html "The Qpid JCA Resource Adapter is shipped in the qpid-java-jca RPM package under the Red Hat Enterprise MRG channel on the Red Hat Network. It is included as part of the MRG Messaging installation. For instructions on how to install MRG Messaging, see the Red Hat Enterprise MRG — Messaging Installation Guide." Is this correct? Or is there a separate way of acquiring the qpid-java-jca package? When is the qpid-java-jca-zip package used instead? Also, could you please elaborate on "installation procedure on different platforms"? What other platforms do you mean? The description is fine. As far as the zip packaged goes, originally this was done to address QE's request for an alternate install mechanism to RPM. Unfortunately, IMO, due to the Brew process we ended up wrapping a zip inside of an RPM which is of little to no value. We are currently discussing plans as to how to provide a real alternative to RPM. Also, now that the adapter is officially upstream at Apache, this provides another packaging alternative for those that want to get the adapter directly rather than use the RPM/MRG distribution. (In reply to comment #3) > We are currently discussing plans as to how to provide a real > alternative to RPM. Also, now that the adapter is officially upstream at > Apache, this provides another packaging alternative for those that want to get > the adapter directly rather than use the RPM/MRG distribution. Will this packaging alternative make it for the 2.2 release? If so, it needs to be documented. Weston, can you please provide the information, or point me to someone who can? No, currently this is just for discussion and has no real plan at this point. It definitely will not be in place prior to 2.2. Released for MRG 2.2 |