Resolution:
Description:
============
This solution describes the JBOSS client jars that are required for JMS connectivity.

Environment:
===========

JBOSS 5.0
TIBCO BusinessWorks 5.x
  
Resolution:
==========
The jbossall-client.jar does not bundle all of the required client jars as in the previous JBOSS versions. You need to reference the following JBOSS client jars in classpath (tibco.env.STD_CP_EXT) of designer.tra:

    $JBOSS_HOME/client/jnp-client.jar
    $JBOSS_HOME/client/jboss-javaee.jar
    $JBOSS_HOME/client/jboss-messaging.jar
    $JBOSS_HOME/client/jboss-remoting.jar
    $JBOSS_HOME/client/jboss-serialization.jar
    $JBOSS_HOME/client/javassist.jar
    $JBOSS_HOME/client/jboss-aop-client.jar
    $JBOSS_HOME/client/trove.jar
    $JBOSS_HOME/client/log4j.jar
    $JBOSS_HOME/client/jboss-logging-spi.jar
    $JBOSS_HOME/client/jboss-logging-log4j.jar
    $JBOSS_HOME/client/jboss-common-core.jar
    $JBOSS_HOME/client/jboss-mdr.jar
    $JBOSS_HOME/client/concurrent.jar
    

Which JBOSS client jars are required for JMS connectivity in TIBCO BusinessWorks?

1). http://docs.jboss.org/jbossas/docs/Installation_And_Getting_Started_Guide/5/html/ch01.html#d0e525

2). http://matthewkwilliams.com/index.php/2010/11/04/jboss-client-jars-for-messaging/