[ 
https://issues.apache.org/jira/browse/SYNAPSE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743551#comment-13743551
 ] 

Hudson commented on SYNAPSE-966:
--------------------------------

ABORTED: Integrated in Synapse - Trunk #4740 (See 
[https://builds.apache.org/job/Synapse%20-%20Trunk/4740/])
Callout mediator improvements - Supporting Synapse Endpoints in callout 
mediator. Applying patches from SYNAPSE-966 SYNAPSE-967 and SYNAPSE-968 
(hiranya: rev 1515263)
* 
/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/SynapseConstants.java
* 
/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/config/xml/CalloutMediatorFactory.java
* 
/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/config/xml/CalloutMediatorSerializer.java
* 
/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/core/axis2/AnonymousServiceFactory.java
* 
/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/core/axis2/Axis2BlockingClient.java
* 
/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/core/axis2/BlockingClientUtils.java
* 
/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/mediators/builtin/CalloutMediator.java
* 
/synapse/trunk/java/modules/core/src/test/java/org/apache/synapse/config/xml/CalloutMediatorSerializationTest.java
* /synapse/trunk/java/modules/documentation/src/site/xdoc/userguide/samples.xml
* 
/synapse/trunk/java/modules/documentation/src/site/xdoc/userguide/samples/sample433.xml
* 
/synapse/trunk/java/modules/integration/src/test/java/org/apache/synapse/samples/framework/TestSamplesHandlerSuite.java
* 
/synapse/trunk/java/modules/integration/src/test/java/org/apache/synapse/samples/framework/tests/advanced/Sample433.java
* 
/synapse/trunk/java/modules/integration/src/test/resources/extras/synapse_sample_433_altered.xml
* /synapse/trunk/java/modules/integration/src/test/resources/sample433.xml
* /synapse/trunk/java/repository/conf/axis2_blocking_client.xml
* /synapse/trunk/java/repository/conf/sample/synapse_sample_433.xml

                
> New Blocking Sender implementation
> ----------------------------------
>
>                 Key: SYNAPSE-966
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-966
>             Project: Synapse
>          Issue Type: New Feature
>            Reporter: Isuru Udana Loku Narangoda
>            Assignee: Hiranya Jayathilaka
>             Fix For: 3.0
>
>         Attachments: SYNAPSE-966.patch
>
>
> 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)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to