[jira] [Resolved] (AXIS2-5881) Small improvement to the listServices.jsp to sort services and operations

     [ https://issues.apache.org/jira/browse/AXIS2-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Lazarski resolved AXIS2-5881.
------------------------------------
    Resolution: Fixed

Fixed on trunk, shipping in 2.0.1. Services are now sorted alphabetically (case-insensitive) on
  the listing page, and operations within each service are also sorted by name.

  Following Andreas's recommendation from February 2025, the sorting is done in
  ListingAgent.processListServices() using a TreeMap with String.CASE_INSENSITIVE_ORDER, and passed
   to the JSP as a sortedServices request attribute — keeping Java logic out of the JSP. The
  operations are sorted into a temporary ArrayList per service. A defensive
  ConcurrentModificationException catch handles the edge case of concurrent hot deployment during
  listing.

  Tested locally on WildFly 32 with 5 deployed services — confirmed sorted output in the browser.

  Thanks to [~JWT007] for the original patch and idea back in 2017, and to [~veithen] for
  the design guidance that shaped the final implementation.


> Small improvement to the listServices.jsp to sort services and operations
> -------------------------------------------------------------------------
>
>                 Key: AXIS2-5881
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5881
>             Project: Axis2
>          Issue Type: Improvement
>    Affects Versions: 1.7.3
>            Reporter: Jeff Thomas
>            Assignee: Robert Lazarski
>            Priority: Minor
>             Fix For: 2.0.1
>
>         Attachments: listServices.jsp, listServices.jsp.patch
>
>
> One thing that has always bothered me about the "services/listServices.jsp" was that it is not sorted ... which means scrolling around looking for the service and/or operations.
> In our build I have updated the listServices.jsp with a few changes to sort the output of services and operations... would just like to suggest the fix be incorporated in the build. (see attachment).  Primarily I replaced the HashMaps with ConcurrentSkipListMap to naturally sort by the keys (ServiceName, OperationName)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)