[SYNAPSE-966] New Blocking Sender implementation

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Assignee: Hiranya Kasub Jayathilaka
• Reporter: Isuru Udana
• Created: 18/Aug/13 13:23
• Updated: 19/Aug/13 05:39
• Resolved: 19/Aug/13 02:29

Description

Currently we have following two main places we use a blocking client to invoke services.
1. Callout Mediator
2. Forwarding Message Processor

Both these components use the axis2 service client to invoke services in a blocking manner.
Since the implementation is very simple, provided functionality is very limited.

Currently we have following major limitations.

• Supports only SOAP
• Message format conversion is not supported
• QOS functionality (WS-Security, WS-A) are not supported
• Cannot specify an endpoint as the service endpoint reference
  (In message processors we can specify an Address endpoint. But none of the other endpoint functionality is supported)

I have implemented a new blocking client which can be used as a common blocking sender for both above components.
This new implementation will provide the following functionality.

• Support all leaf endpoint types
• Support for REST
• Support Endpoint functionality.

• Endpoint format conversions (soap11,soap12,pox, etc.)
• WS-Security, WS-A
• Endpoint Timeout (nhttp transport specific functionality is not supported)

• message format conversions (ability to use messageType/ContentType properties)

Sub-Tasks

• Migrating Callout Mediator to new blocking client implementation: Resolved
• Sample and an integration test for Callout mediator - Invoke a service using a defined Endpoint: Resolved