Hi, We will be doing the Axis2 1.4.1 release on Axis2 1.4 branch [1] and according to the mailing list and JIRA, following issues are requested to be fixed in Axis2 1.4.1 release.
Fixed in the trunk https://issues.apache.org/jira/browse/AXIS2-3914 - Remove servlet-api-2.3.jar from axis2.war https://issues.apache.org/jira/browse/AXIS2-3908 - Prevent StackOverFlowError in AxisServlet https://issues.apache.org/jira/browse/AXIS2-3887 - The servlet transport does not set the HTTP response code to 500 when a SOAP fault is returned https://issues.apache.org/jira/browse/AXIS2-3870 - Memory Leak using ServiceClient https://issues.apache.org/jira/browse/AXIS2-3819 - Parameter ordering screws up in the genarated WSDL when the original WSDL has multiple message parts https://issues.apache.org/jira/browse/AXIS2-3859 - If a service is deployed using WSDL 2.0 the genarated ?wsdl2 does not show the endpoints https://issues.apache.org/jira/browse/AXIS2-3915 - Policies attached using the wsp:PolicyURIs attribute are not included in the code generated Stub Not fixed in the trunk https://issues.apache.org/jira/browse/AXIS2-3905 - Requests coming through the old EPR are not dispatched to a binding https://issues.apache.org/jira/browse/AXIS2-3913 - Multiple policies not serialized correctly at service level (as portType PolicyURIs attribute) https://issues.apache.org/jira/browse/AXIS2-3907 - Message level policy not serialized correctly in wsdl 1.1 https://issues.apache.org/jira/browse/AXIS2-3867 - Axis2 goes into a endless loop if httpLocations such as whttp:location="{name"} is used https://issues.apache.org/jira/browse/AXIS2-3877 - whttp:locations do not take into the account correct endpoint urls of the form service.endpoint https://issues.apache.org/jira/browse/AXIS2-3903 - rfc-2822 issues with Mail transport All these are bug fixes and I think we will be able to get them in to Axis2 1.4.1 if we get patches for these issues against Axis2 1.4 branch. You can directly commit the patches to the branch but please update this thread if you do so with the issue you fixed. I am plaining put a RC on Friday 25th, so I think it is great if we can code freeze the branch around 23rd. I think we will be able do the release somewhere around 1st of August. Your comments are most well come. thanks, nandana [1] - https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_4/
