You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/09/20 11:43:51 UTC
[jira] [Commented] (ISIS-443) Provide the ability to group domain
services into logical menus, using @MemberOrder.
[ https://issues.apache.org/jira/browse/ISIS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772907#comment-13772907 ]
ASF subversion and git services commented on ISIS-443:
------------------------------------------------------
Commit 556534ebe074857ab6ed61aa0eb0cfd8c48e2c5b in branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=556534e ]
ISIS-443: logical application menus should honour registered service order
> Provide the ability to group domain services into logical menus, using @MemberOrder.
> ------------------------------------------------------------------------------------
>
> Key: ISIS-443
> URL: https://issues.apache.org/jira/browse/ISIS-443
> Project: Isis
> Issue Type: New Feature
> Components: Viewer: Wicket
> Affects Versions: viewer-wicket-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.3.0
>
>
> Suppose we have two closely related domain services, each servicing a different entity, eg:
> Property and Unit.
> We would like these actions to appear as a single menu, eg "Assets".
> The idea is to use @MemberOrder for this, eg:
> class Property {
> @MemberOrder(name="Assets", sequence="1")
> public Property findProperty( ... ) { ... }
> @MemberOrder(name="Assets", sequence="2")
> public Property newProperty( ... ) { ... }
> }
> and
> class Unit {
> @MemberOrder(name="Assets", sequence="3")
> public Unit findUnit( ... ) { ... }
> @MemberOrder(name="Assets", sequence="4")
> public Unit newUnit( ... ) { ... }
> }
> These four actions would then appear under an "Assets" menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira