Resource-adapter configred in EAP 7 throws ClassNotFoundException for all classes of javax.jms.*

Solution Unverified - Updated -

Issue

I am working on a PoC with jboss-eap-7.0.0 and was just . To do that, I did the following while integrating EAP 7 with ibm websphere mq:
- deploy wmq.jmsra.rar (wmq resource adapter)
- configure a resource adapter in subsystem resource-adapters for outbound communication in standalone.xml
- deploy a sender bean for outbound communication
- deploy an mdb for inbound communication

When deploying to EAP-7 I got ClassNotFoundException for all classes of javax.jms.* (e.g. JmsException, ConnectionFactory, ...).

I could get it working by adding <module name="javax.jms.api" export="true" ></module> to dependencies list of jboss-deployment-structure.xml.

My question:
Before EAP-7, this dependency was added automatically, nothing had to be done by the developer. A discovery mechanism recognized that jms was used and the dependency was added automatically. Now with EAP-7, this does apparently not work anymore. Will this issue be resolved? If an issue for this already exists, please point me to the issue, otherwise, I would like to open one.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.