Start bringing up Tuscany version of JMS transport so the setMessageListener not allowed in a JEE container can be fixed

git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@774701 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 14 insertions, 0 deletions

diff --git a/branches/sca-java-1.x/modules/binding-ws-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2/jms/README b/branches/sca-java-1.x/modules/binding-ws-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2/jms/README
new file mode 100644
index 0000000000..5df1751298
--- /dev/null
+++ b/branches/sca-java-1.x/modules/binding-ws-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2/jms/README
@@ -0,0 +1,14 @@
+The classes in this package are a copy of the same classes from the 

+Axis2 package org.apache.axis2.transport.jms in the Axis2 1.4.1 release.

+

+The only change is in the listenOnDestination method in JMSConnectionFactory

+to use Tuscany threads instead of the setMessageListener call approach when

+running in a JEE container where setMessageListener is prohibited. There are

+several classes copied in this Tuscany package as many of the constructors

+and methods are not public so we can't just subclass to fix the problem.

+

+In Axis2 1.5 and the new separately released JMS transport will fix this

+problem so when we move up to that in Tuscany we can get rid of this package. 

+

+

+