README-EJB-JMS.txt 1.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. jboss-client.jar is a combined client jar for JBoss AS7, for use in non-maven environments. This jar should be used
  2. with standalone clients only, not with deployments are that deployed to an AS7 instance.
  3. This jar contains the classes required for remote JMS and EJB usage, and consists of the following shaded artifacts:
  4. org.jboss.spec.javax.jms:jboss-jms-api_1.1_spec
  5. org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec
  6. org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec
  7. org.jboss:jboss-ejb-client
  8. org.jboss:jboss-remote-naming
  9. org.jboss.logging:jboss-logging
  10. org.jboss.marshalling:jboss-marshalling
  11. org.jboss.marshalling:jboss-marshalling-river
  12. org.jboss.remoting3:jboss-remoting
  13. org.jboss.remoting3:remoting-jmx
  14. org.jboss.sasl:jboss-sasl
  15. org.jboss.xnio:xnio-api
  16. org.jboss.xnio:xnio-nio
  17. org.jboss.netty:netty
  18. org.hornetq:hornetq-core-client
  19. org.hornetq:hornetq-jms-client
  20. Maven users should not use this jar, but should use the following BOM dependencies instead
  21. <dependencies>
  22. <dependency>
  23. <groupId>org.jboss.as</groupId>
  24. <artifactId>jboss-as-ejb-client-bom</artifactId>
  25. <type>pom</type>
  26. </dependency>
  27. <dependency>
  28. <groupId>org.jboss.as</groupId>
  29. <artifactId>jboss-as-jms-client-bom</artifactId>
  30. <type>pom</type>
  31. </dependency>
  32. </dependencies>
  33. This is because using maven with a shaded jar has a very high chance of causing class version conflicts, which is why
  34. we do not publish this jar to the maven repository.