Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 816632

Summary:	Torquebox: Messaging module depends on JMS 1.1, EAP6 ER5 and newer use JMS 1.2
Product:	[Retired] JBoss Enterprise WFK Platform 2	Reporter:	Oliver Kišš <okiss>
Component:	TorqueBox	Assignee:	Bob McWhirter <bmcwhirt>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Oliver Kišš <okiss>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.0.0.ER4	CC:	kpiwko, oskutka
Target Milestone:	---
Target Release:	2.0.0.ER7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-04 11:27:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Oliver Kišš 2012-04-26 14:47:21 UTC

Description of problem:

Torquebox Messaging module in Torquebox 2.0.1 depends on JMS 1.1
EAP 6 uses JMS 1.2 since ER5


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

Comment 1 Karel Piwko 2012-04-27 07:24:50 UTC

This renders project unusable with EAP ER5 and newer using EAP Maven repository zip.

Comment 2 Bob McWhirter 2012-05-01 14:04:18 UTC

We are unsure where this mismatch is coming from, as AS7 appears to still use JMS 1.1.

Any idea?

Comment 3 Bob McWhirter 2012-05-01 14:07:40 UTC

Additionally, i cannot find a JMS 1.2 spec jar in the .org Nexus maven repository:

https://repository.jboss.org/nexus/index.html#nexus-search;quick~jboss-jms-api

Comment 5 Oliver Kišš 2012-06-04 11:27:23 UTC

I am sorry for the confusion. I meant messaging subsystem, not JMS.

This is now fixed in Torquebox 2.0.3.redhat.1 which is based on newer versions of EAP.