[AXIS2-2443] Axis2 TCP support is in experimental level - MTOM support disabled - required for AXIS2/WSE3 interop over TCP

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.1.1
• Component/s: transports
• Environment: Windows XP, SP2; .NET2 WSE3; AXIS2 1.1.1
• Assignee: Nanayakkara Kuruppuge Thilina Gunarathne
• Reporter: Richard Beaumont
• Created: 30/Mar/07 08:58
• Updated: 02/Jul/16 13:13
• Resolved: 02/Jul/16 13:13

Description

From issue AXIS-1469 it would appear that MTOM support over TCP has been disabled. As this is configurable in software and via config files not sure why it has been removed so completely.

The problem:
I wish to communicated from an AXIS2 client to WSE3 over TCP. Thilina Gunarathne informs me that this is working fine over HTTP. However, that will require an ISS server and the whole point of using WSE3 is to not required an IIS server- hence the comms is over TCP. This works fine in WSE3 client to WSE3 webservice. When communucating over TCP WSE3 will MTOM encode messages, hence requirement for MTOM support when using TCP.

To allow for AXIS2/WSE3 interop over TCP the current level of support for TCP in AXIS2 needs to be improved. I understamd that currently it is 'in experimental level' due to the absence of a published TCP Binding for SOAP.

If anyone has examples of AXIS2/WSE3 interop over TCP please get in touch - though I would be very surprise if it is using AXIS2 1.1.1.