Bug 816632 - Torquebox: Messaging module depends on JMS 1.1, EAP6 ER5 and newer use JMS 1.2
Summary: Torquebox: Messaging module depends on JMS 1.1, EAP6 ER5 and newer use JMS 1.2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: TorqueBox
Version: 2.0.0.ER4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 2.0.0.ER7
Assignee: Bob McWhirter
QA Contact: Oliver Kišš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-26 14:47 UTC by Oliver Kišš
Modified: 2015-08-02 23:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-06-04 11:27:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.