Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Date: Thu, 7 Sep 2017 10:52:00 +0000 (UTC)
From: "Jeff Thomas (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Message-ID: <JIRA.13100133.1504701909000.48668.1504781520375@Atlassian.JIRA>
In-Reply-To: <JIRA.13100133.1504701909000@Atlassian.JIRA>
References: <JIRA.13100133.1504701909000@Atlassian.JIRA> <JIRA.13100133.1504701909341@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AXIS2-5881) Small improvement to the
 listServices.jsp to sort services and operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 07 Sep 2017 10:52:06 -0000


    [ https://issues.apache.org/jira/browse/AXIS2-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156801#comment-16156801 ] 

Jeff Thomas commented on AXIS2-5881:
------------------------------------

Hi Thorsten,

1. I guess I could have used TreeMap.   I just chose the ConcurrentSkipListMap for the failsafe iterators.

2- Can't answer that one... we actually toss out AxisOperations we don't expose during Service-Generation and don't use the TAG_EXPOSE option... although I didn't know about it until you mentioned it here :)

Cheers, Jeff


> 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
>            Priority: Minor
>         Attachments: listServices.jsp
>
>
> 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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org