synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isuru Udana Loku Narangoda (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SYNAPSE-966) New Blocking Sender implementation
Date Sun, 18 Aug 2013 13:32:48 GMT

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

Isuru Udana Loku Narangoda edited comment on SYNAPSE-966 at 8/18/13 1:30 PM:
-----------------------------------------------------------------------------

Please find this improvement from the attachment.
I have added a new axis2.xml (axis2_blocking_client.xml) instead of using the usual blocking
client axis2.xml which is placed in samples directory as it is not the ideal place to have
it.
                
      was (Author: isudana):
    Please find this improvement from the attachment.
I have added a new axis2.xml (axis2_blocking_client.xml) instead of using the usual blocking
client axis2.xml which is placed in samples directory is not the ideal place to have it.
                  
> 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
>         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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message