MulipleEntryHashMap s' get operation removes the value from the map

2011-06-20 Thread Pradeep Fernando
Hi devs, In the axis2 x-form-url-encoded builder it stores HTTP post request values (in the message body) in MultipleEntryHashMap and attach to the axis2MessageContext using a property. So when I send a POST request with a key,value pairs in the message body, axis2 builds a SOAP env with an empty

[AXIS2] WSDL Port Address generation between 1.3 and 1.5

2011-06-20 Thread Nadir Amra
In Axis 1.3, the Axis2 engine generated the port from the incoming request, as far as I know. For example, assume the following: Axis2 running in server listening on port 10051 HTTP server front-ending the Axis2 server running and listening on port 10061 services.xml file has: false

Re: WSDL generation for the services exposed only in local transport

2011-06-20 Thread Hiranya Jayathilaka
Well to be honest I don't really see a strong use case in Synapse for this (perhaps we should first discuss this on synapse-dev). Why do we need to expose a service only over local transport? What does that give us in addition to what we already have? What problem are we trying to solve here? A se

[jira] [Created] (AXIS2-5073) HttpTransportProperties not available in axis2 1.6 (and even older versions) - still tutorials reference it

2011-06-20 Thread Ttothe Wee (JIRA)
HttpTransportProperties not available in axis2 1.6 (and even older versions) - still tutorials reference it --- Key: AXIS2-5073 URL: https://issues.apache.org/