-
Documentation
-
Resolution: Done
-
Major
-
7.1.0.GA
While the documentation for the Generic Resource Adapter and Tibco integration was correct for JBoss EAP 6.4, errors have been introduced in the EAP 7.1 documentation.
Maybe I'm missing something, but in the 6.4 documentation (I wish that I could refer to the code samples by number), the Tibco jars are placed in the 'org.jboss.genericjms.provider' module. This makes sense, as the Generic Resource Adapter (GRA) module includes (optionally) the 'org.jboss.genericjms.provider' . This is the module that provides the GRA with the Tibco client classes.
In the 7.1 documentation, the two Tibco jars are placed in the 'com.tibco.tibjms' module. I don't understand how this module is provided to the GRA.
In the 6.4 documentation, the GRA is configured as the JCA:
<resource-adapter id="org.jboss.genericjms"> <module slot="main" id="org.jboss.genericjms"/>
While in the 7.1 documentation, the 'com.tibco.tibjms' module is deployed as a resource adapter?
/subsystem=resource-adapters/resource-adapter=com.tibco.tibjms:add(module=com.tibco.tibjms,transaction-support=XATransaction)
In the 7.1 documentation, for the external naming context, a module named 'module=my.generic.JMSAdapter' is used. This is not defined anywhere.
The 6.4 documentation has 'module="org.jboss.genericjms.provider"''. Which is correct - this is the module that has the Tibco client jars.
- clones
-
JBEAP-14299 [CD13] Incorrect instructions for Configuring the Generic Resouce Adapter
- Closed
- is cloned by
-
JBEAP-14572 [7.0] Incorrect instructions for Configuring the Generic Resouce Adapter
- Closed
- relates to
-
JBEAP-7215 [DOC RFE] Provide Support for a Generic Resource Adapter for use with a 3rd Party JMS Provider Tibco EMS 8
- Closed