Hi Alelikov,
AxisServlet sets itself as HTTP transport receiver and does not take the transport receiver definitions in axis2.xml into account. I've simply changed the AxisServlet for enabling it to initialize all the transport receivers defined in axis2.xml, but HTTP. For HTTP, just left it as is. Logs convinced me that it worked :)
I've provided this solution as patch to the mentioned issue(AXIS2-1488). Eventhough it would not be part of Axis2 distro, I hope, you may use it as work around for now.
Regards,
Ali Sadik Kumlali
AxisServlet sets itself as HTTP transport receiver and does not take the transport receiver definitions in axis2.xml into account. I've simply changed the AxisServlet for enabling it to initialize all the transport receivers defined in axis2.xml, but HTTP. For HTTP, just left it as is. Logs convinced me that it worked :)
I've provided this solution as patch to the mentioned issue(AXIS2-1488). Eventhough it would not be part of Axis2 distro, I hope, you may use it as work around for now.
Regards,
Ali Sadik Kumlali
----- Original Message ----
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Monday, November 13, 2006 10:03:04 PM
Subject: How to enable JMS transport in WAR distro?
Hi,
Does anyone know how to work around this "not a blocker"?
http://issues.apache.org/jira/browse/AXIS2-1488
Thanks in advance,
AL
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Monday, November 13, 2006 10:03:04 PM
Subject: How to enable JMS transport in WAR distro?
Hi,
Does anyone know how to work around this "not a blocker"?
http://issues.apache.org/jira/browse/AXIS2-1488
Thanks in advance,
AL
