You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Luciano Resende (JIRA)" <de...@tuscany.apache.org> on 2009/05/13 01:06:45 UTC

[jira] Resolved: (TUSCANY-2968) Provide support for binding.http based on OASIS draft specification

     [ https://issues.apache.org/jira/browse/TUSCANY-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luciano Resende resolved TUSCANY-2968.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: Java-SCA-1.5

Introduced wire format and operation selector on top of current binding http based on what was done for JMS binding

> Provide support for binding.http based on OASIS draft specification
> -------------------------------------------------------------------
>
>                 Key: TUSCANY-2968
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2968
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java SCA HTTP Binding
>    Affects Versions: Java-SCA-Next
>            Reporter: Luciano Resende
>            Assignee: Luciano Resende
>             Fix For: Java-SCA-1.5, Java-SCA-Next
>
>
>  HTTP binding specification :
> http://lists.oasis-open.org/archives/sca-bindings/200810/msg00078.html
>                                                                            
>                                                                            
>  I wonder if we can support part of                                        
>  the specification so that we can                                          
>  have a generic binding based on                                           
>  HTTP protocol , use the wireFormat                                        
>  and operationSelector definition to                                       
>  support a specific mapping between                                        
>  messageBody and SCA services...                                           
>                                                                            
>  The part of the schema interests me                                       
>  is:                                                                       
>                                                                            
>  <binding.http uri="xs:anyURI"? ...>                                        
>      <wireFormat/>?                                                         
>      <operationSelector/>?                                                  
>      <response>                                                             
>          <wireFormat>?                                                      
>      </response>?                                                          
>  </binding.http>                                                            
>                                                                            
> One sample of using this binding will be converting the JSON-RPC binding to
> be an HTTP binding with the wireFormat of JSON-PRC:
> <component name="Catalog">
>    <implementation.java class="services.FruitsCatalogImpl"/>
>    <service name="Catalog">
>       <t:binding.http uri="http://localhost:8080/Catalog";>
>          <wireFormat.jsonrpc/>
>       </t:binding.http>
>    </service>
> </component>
> <reference name="catalog" target="Catalog">
>       <t:binding.http>
>             <wireFormat.jsonrpc/>
>       </t:binding.http>
>  </reference>
> I noticed there are some discussion on the list last year on this:
> More details on the following thread
>    http://www.mail-archive.com/dev@tuscany.apache.org/msg05921.html
>    http://www.mail-archive.com/dev@tuscany.apache.org/msg03037.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.