[
http://jira.jboss.com/jira/browse/JBWS-1911?page=comments#action_12396729 ]
Heiko Braun commented on JBWS-1911:
-----------------------------------
The endpoint implementation requires an explicit listener interface:
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue
= "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue =
"queue/RequestQueue")
},
messageListenerInterface = javax.jms.MessageListener.class
)
Support the JMS transport with JAX-WS
--------------------------------------
Key: JBWS-1911
URL:
http://jira.jboss.com/jira/browse/JBWS-1911
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-2.0.1
Environment: All Mid Range platforms ( AIX, Linux etc)
Reporter: Gopi Chand Uppala
Assigned To: Thomas Diesler
Fix For: jbossws-native-2.0.3
AT&T is in a process of developing a web services framework for the Enterprise usage
. The Requirements for this framework includes the support of JMS transport bindings with
JAX-WS . JBoss EAP 4.3 (Jbossws 2.0.1) is being considered as one of the target
containers for this framework and the inability to support the JMS transport with JAX-WS
would eliminate JBoss as one of the three target Application Servers for web services
usage in AT&T. This is very critical feature for AT&T and we would like Jboss to
support it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira