Patch axis to ensure that the available methods are kept in the same order on each WSDL generation

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.0.0 DXP FP89, 7.0.10.13 DXP SP13, 7.0.X, 7.1.10 DXP FP16, 7.1.X, 7.2.10 DXP FP4, 7.2.X, 7.3.0 CE GA1, 7.3.10 DXP GA1, Master
• Component/s: Web Services > SOAP
• Labels:
  • ee-ts
  • liferay-dxp-70-sp13
  • liferay-fixpack-de-89-7010
  • liferay-fixpack-dxp-16-7110
  • liferay-fixpack-dxp-4-7210
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/81992

This issue is very similar to the one reported in: LPS-104001

After patching a portal 7.1 from dxp-10 to dxp-13, there are changes compared to directly patching to dxp-13: there is a difference in generating a WSDL file for Portal_UserService.

It's not a big difference, as it means that getGroupUsers() method's 2 versions' are changing places in order, but it means that the same endpoint maps to a different method based on its parameter list.