Asanka, I've been looking at the notion of using the axis2 "messageType" property with a value of "application/x-www-form-urlencoded" to drive the use of the "XFormURLEncodedFormatter". Using this property isn't currently supported by the 1.0 release of Synapse: the cloneForSend method on Axis2FlexibleMEPClient doesn't "clone" that property. I made a small change to my local sources for testing. This put me part of the way there. At the moment it seems as if the HTTP transfer-encoding of chunked is goofing up the FORM post. How do I control when a given request uses transfer-encoding of chunked or not.
Thanks, Michael -----Original Message----- From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 3:53 PM To: [email protected] Subject: Re: Synapse with HTTP GET query string and POST with form data Michael Sorry, I have been traveling over the weekend and thus the delay to respond. Well, we do support POST in the form of XML/HTTP right now. However, I feel that what you are looking for may be something like a "form" POST? Could you get a TCPMon dump of such a request and share with us? If your payload is going to be non-XML you would need to probably write a transformation mediator to perform a custom transform thanks asankha Michael Griffin wrote: Basically, some of my business partners aren't yet on the XML bandwagon :-( and require service invocations as HTTP "form" POSTS - as if I filled out an HTML FORM with a method of POST and some number of INPUT fields. Maybe the answer is the I have to create a custom mediator. I'm just looking for some direction because I would really like to be able to use Synapse. -----Original Message----- From: Ruwan Linton [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 11:01 AM To: [email protected] Subject: Re: Synapse with HTTP GET query string and POST with form data Hi Michael, On 6/25/07, Michael Griffin <[EMAIL PROTECTED]> wrote: Asankha, I'll submit a feature request for the GET support. But for the POX form POST, how might I create the "form" data. I was thinking about using the script mediator but couldn't find a way that allowed me to set the content... Let me know. I am not clear at this point. Can you please explain your scenario a bit more. If what you want is to call a POX endpoint upon receiving a SOAP request to Synapse, Asankha's answer is the ideal one. That is you need to enforce POX in that endpoint definition inside Synapse. <endpoint><address uri="$POX_EP_URI" format="pox"/></endpoint> the above configuration will ensure that the service under the $POX_EP_URI is getting only POX even though the request to synapse is on SOAP. If this is not what you want to do. Please explain your exact scenario a bit more. Thanks, Ruwan. Thanks, Michael -----Original Message----- From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Saturday, June 23, 2007 12:58 AM To: [email protected] Subject: Re: Synapse with HTTP GET query string and POST with form data Michael I would like to know how to get Synapse to use an endpoint that is is expecting an HTTP "form" POST or an HTTP GET request.Use format as "pox" in the endpoint definition. <address uri="endpoint-address" format="soap|soap11|soap12|pox" [optimize="mtom|swa"]> Ideally I would like to send a GET with a query string built from the inbound SOAP message (coming into Synapse) and return Plain Old XML. However, this would not provide you GET support but POST. We could implement GET support if you think its a common use case for our 1.1 revision we are planning next. I would also like to transform an inbound SOAP request into an HTTP form POST that returns POX. This would work with the above setting. asankha --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
