Asankha, will you be able to go through the patch... and do a regression test of the REST proxy scenarios, or if you could give me a pointer on the functionality that might brake due to this I could have a look at it as well.
Thanks, Ruwan On Wed, Jun 3, 2009 at 2:58 PM, Keith Godwin Chapman (JIRA) <[email protected] > wrote: > > [ > https://issues.apache.org/jira/browse/SYNAPSE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715871#action_12715871] > > Keith Godwin Chapman commented on SYNAPSE-555: > ---------------------------------------------- > > Yes this does fix https://issues.apache.org/jira/browse/SYNAPSE-431. > Verified it. > > "Right now Synapse can work as a full REST proxy as expected". That is not > correct ;). That is the reason that I opened this jira. If a user provides a > wsdl and if the schemaTargetnamespace of that WSDL does not use the Axis2 > default of http://org.apache.axis2/xsd it will not work. The Axis2 code > handles this case, that is the reason I thought of integrating it into > Synapse. > > Also with this new patch you will be able to use the complete support in > WSDL 2.0 (including htttpLocations, which would not work with the existing > code). > > > When doing REST invocation on Proxy Services 'namespace mismatch' error > thrown > > > ------------------------------------------------------------------------------ > > > > Key: SYNAPSE-555 > > URL: https://issues.apache.org/jira/browse/SYNAPSE-555 > > Project: Synapse > > Issue Type: Bug > > Components: Core > > Reporter: Keith Godwin Chapman > > Priority: Critical > > Fix For: 1.3 > > > > Attachments: patch.txt > > > > > > If a proxy service is created in the following manner (Always convert > incoming request to SOAP 1.1) > > <?xml version="1.0" encoding="UTF-8"?> > > <syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse";> > > <syn:proxy name="test2" transports="https http" startOnLoad="true" > trace="disable"> > > <syn:target> > > <syn:endpoint> > > <syn:address uri=" > http://localhost:9000/services/SimpleStockQuoteService"; format="soap11"/> > > </syn:endpoint> > > <syn:inSequence> > > <syn:log/> > > </syn:inSequence> > > <syn:outSequence> > > <syn:log/> > > </syn:outSequence> > > </syn:target> > > <syn:publishWSDL uri=" > http://localhost:9000/services/SimpleStockQuoteService?wsdl"/> > > </syn:proxy> > > <syn:sequence name="main"> > > <syn:in> > > <syn:log level="full"/> > > <syn:filter source="get-property('To')" > regex="http://localhost:9000.*";> > > <syn:send/> > > </syn:filter> > > </syn:in> > > <syn:out> > > <syn:send/> > > </syn:out> > > </syn:sequence> > > <syn:sequence name="fault"> > > <syn:log/> > > </syn:sequence> > > </syn:definitions> > > The SOAP message sent out by Synapse does not conform to the WSDL. Hence > the error described in https://wso2.org/jira/browse/CARBON-3931 occurs. > The bug was in the way synapse tries to build the SOAP message from the REST > request. This works properly in plain Axis2, but synapse was using its own > logic to build the message. > > This patch fixes Synapse such that it uses the logic in Axis2 to handle > REST request. This bug has been in Synapse for a long time but surfaced due > to the change in namespace in the sample WSDL. > > This patch also addresses an issue in Handling of the DELETE method. the > same axis2 logic can be called for this method. > > This > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Ruwan Linton Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
