[jira] [Created] (ISIS-430) Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation.
Dan Haywood created ISIS-430: Summary: Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation. Key: ISIS-430 URL: https://issues.apache.org/jira/browse/ISIS-430 Project: Isis Issue Type: New Feature Components: Archetypes, Core, Viewer: Wicket Affects Versions: core-1.2.0, viewer-wicket-1.2.0, archetype-wrj-1.0.2 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: archetype-wrj-1.0.3, viewer-wicket-1.3.0, core-1.3.0 -- 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
[jira] [Resolved] (ISIS-430) Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation.
[ https://issues.apache.org/jira/browse/ISIS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-430. -- Resolution: Fixed Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation. - Key: ISIS-430 URL: https://issues.apache.org/jira/browse/ISIS-430 Project: Isis Issue Type: New Feature Components: Archetypes, Core, Viewer: Wicket Affects Versions: archetype-wrj-1.0.2, viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: archetype-wrj-1.0.3, viewer-wicket-1.3.0, core-1.3.0 -- 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
[jira] [Updated] (ISIS-430) Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation.
[ https://issues.apache.org/jira/browse/ISIS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-430: - Affects Version/s: (was: archetype-wrj-1.0.2) archetype-wrj-1.0.3 Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation. - Key: ISIS-430 URL: https://issues.apache.org/jira/browse/ISIS-430 Project: Isis Issue Type: New Feature Components: Archetypes, Core, Viewer: Wicket Affects Versions: archetype-wrj-1.0.3, viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: archetype-wrj-1.0.4, viewer-wicket-1.3.0, core-1.3.0 -- 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
[jira] [Updated] (ISIS-430) Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation.
[ https://issues.apache.org/jira/browse/ISIS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-430: - Fix Version/s: (was: archetype-wrj-1.0.3) archetype-wrj-1.0.4 Allow the sort order for SortedSet parented collections to be overridden with a new @SortedBy annotation. - Key: ISIS-430 URL: https://issues.apache.org/jira/browse/ISIS-430 Project: Isis Issue Type: New Feature Components: Archetypes, Core, Viewer: Wicket Affects Versions: archetype-wrj-1.0.2, viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: archetype-wrj-1.0.4, viewer-wicket-1.3.0, core-1.3.0 -- 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
[jira] [Commented] (ISIS-421) Write TCK tests for Restful Objects viewer
[ https://issues.apache.org/jira/browse/ISIS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679421#comment-13679421 ] Dan Haywood commented on ISIS-421: -- Applied, thanks. A few very minor comments... 1. when creating a commit message, use ISIS-xxx: as the prefix. 2. some of the tab formatting was a little off in one of the files. Please use the settings in [1] 3. you could have removed the _TODO suffix, since these are now done. (I've done this in a follow-up commit) Cheers Dan [1] http://isis.apache.org/contributors/development-environment.html Write TCK tests for Restful Objects viewer -- Key: ISIS-421 URL: https://issues.apache.org/jira/browse/ISIS-421 Project: Isis Issue Type: Improvement Components: Viewer: RestfulObjects Affects Versions: viewer-restfulobjects-2.0.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: viewer-restfulobjects-2.1.0 Attachments: ISIS-421_Get_thenResponseCode_200_TODO.patch Implement TCK tests for RO viewer, as found in: https://github.com/apache/isis/tree/master/component/viewer/restfulobjects/tck/src/test/java/org/apache/isis/viewer/restfulobjects/tck -- 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
[jira] [Commented] (ISIS-421) Write TCK tests for Restful Objects viewer
[ https://issues.apache.org/jira/browse/ISIS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679424#comment-13679424 ] ASF subversion and git services commented on ISIS-421: -- Commit 734950d72bb293dd5981aae4b7dbc84073d21cbc in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=734950d ] ISIS-421: renaming completed tests, reformatting one or two of them. Write TCK tests for Restful Objects viewer -- Key: ISIS-421 URL: https://issues.apache.org/jira/browse/ISIS-421 Project: Isis Issue Type: Improvement Components: Viewer: RestfulObjects Affects Versions: viewer-restfulobjects-2.0.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: viewer-restfulobjects-2.1.0 Attachments: ISIS-421_Get_thenResponseCode_200_TODO.patch Implement TCK tests for RO viewer, as found in: https://github.com/apache/isis/tree/master/component/viewer/restfulobjects/tck/src/test/java/org/apache/isis/viewer/restfulobjects/tck -- 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
[jira] [Created] (ISIS-431) A boolean atribute should never be mandatory
Jeroen van der Wal created ISIS-431: --- Summary: A boolean atribute should never be mandatory Key: ISIS-431 URL: https://issues.apache.org/jira/browse/ISIS-431 Project: Isis Issue Type: Bug Components: Viewer: Wicket Affects Versions: viewer-wicket-2.0.0 Reporter: Jeroen van der Wal Assignee: Dan Haywood Priority: Minor A boolean attribute only has two states and when the @Optional annotation is omitted and the boolean is set to false, eg the checkbox is empty, it's impossible to save the object. -- 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
[jira] [Commented] (ISIS-431) A boolean atribute should never be mandatory
[
https://issues.apache.org/jira/browse/ISIS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679442#comment-13679442
]
Dan Haywood commented on ISIS-431:
--
The workaround is to declare the type as Boolean, annotate @Optional, and use
(val != null val.booleanValue()) to determine if true:
void foo(@Optional Boolean flag) {
setFoo(flag !=null flag.booleanValue());
}
A boolean atribute should never be mandatory
Key: ISIS-431
URL: https://issues.apache.org/jira/browse/ISIS-431
Project: Isis
Issue Type: Bug
Components: Viewer: Wicket
Affects Versions: viewer-wicket-2.0.0
Reporter: Jeroen van der Wal
Assignee: Dan Haywood
Priority: Minor
A boolean attribute only has two states and when the @Optional annotation is
omitted and the boolean is set to false, eg the checkbox is empty, it's
impossible to save the object.
--
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
[jira] [Commented] (ISIS-431) A boolean atribute should never be mandatory
[ https://issues.apache.org/jira/browse/ISIS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679443#comment-13679443 ] Dan Haywood commented on ISIS-431: -- I think the deeper problem here is that our booleans are not tri-valued. We might want to say that a boolean is explicitly specified as either false or true... which means that its initial value must be neither so that we can detect if it has been entered or not. A boolean atribute should never be mandatory Key: ISIS-431 URL: https://issues.apache.org/jira/browse/ISIS-431 Project: Isis Issue Type: Bug Components: Viewer: Wicket Affects Versions: viewer-wicket-2.0.0 Reporter: Jeroen van der Wal Assignee: Dan Haywood Priority: Minor A boolean attribute only has two states and when the @Optional annotation is omitted and the boolean is set to false, eg the checkbox is empty, it's impossible to save the object. -- 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
[jira] [Updated] (ISIS-431) A boolean atribute should never be mandatory
[ https://issues.apache.org/jira/browse/ISIS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-431: - Fix Version/s: viewer-wicket-2.0.0 Affects Version/s: (was: viewer-wicket-2.0.0) viewer-wicket-1.2.0 A boolean atribute should never be mandatory Key: ISIS-431 URL: https://issues.apache.org/jira/browse/ISIS-431 Project: Isis Issue Type: Bug Components: Viewer: Wicket Affects Versions: viewer-wicket-1.2.0 Reporter: Jeroen van der Wal Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-2.0.0 A boolean attribute only has two states and when the @Optional annotation is omitted and the boolean is set to false, eg the checkbox is empty, it's impossible to save the object. -- 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
[jira] [Created] (ISIS-432) In the wicket viewer, table columns should be sortable
Dan Haywood created ISIS-432: Summary: In the wicket viewer, table columns should be sortable Key: ISIS-432 URL: https://issues.apache.org/jira/browse/ISIS-432 Project: Isis Issue Type: New Feature Components: Viewer: Wicket Affects Versions: viewer-wicket-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.3.0 -- 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
[jira] [Commented] (ISIS-432) In the wicket viewer, table columns should be sortable
[ https://issues.apache.org/jira/browse/ISIS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679472#comment-13679472 ] ASF subversion and git services commented on ISIS-432: -- Commit 5a85a303b09e0e10582f6902d982b7554505f199 in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5a85a30 ] ISIS-432: table columns now sortable. In the wicket viewer, table columns should be sortable -- Key: ISIS-432 URL: https://issues.apache.org/jira/browse/ISIS-432 Project: Isis Issue Type: New Feature Components: Viewer: Wicket Affects Versions: viewer-wicket-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.3.0 -- 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
[jira] [Resolved] (ISIS-432) In the wicket viewer, table columns should be sortable
[ https://issues.apache.org/jira/browse/ISIS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-432. -- Resolution: Fixed In the wicket viewer, table columns should be sortable -- Key: ISIS-432 URL: https://issues.apache.org/jira/browse/ISIS-432 Project: Isis Issue Type: New Feature Components: Viewer: Wicket Affects Versions: viewer-wicket-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.3.0 -- 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
[jira] [Created] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
Dan Haywood created ISIS-433: Summary: Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Commented] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679563#comment-13679563 ] ASF subversion and git services commented on ISIS-433: -- Commit 9bda4c3f310945d3045a8433726facf0652b8613 in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=9bda4c3 ] ISIS-433: Autocomplete prefix method for action parameters Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Resolved] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-433. -- Resolution: Fixed Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Updated] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-433: - Affects Version/s: viewer-wicket-1.2.0 core-1.2.0 Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Affects Versions: viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Updated] (ISIS-434) Provide context-specific autoComplete through prefixed methods on properties
[
https://issues.apache.org/jira/browse/ISIS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-434:
-
Affects Version/s: viewer-wicket-1.2.0
core-1.2.0
Provide context-specific autoComplete through prefixed methods on properties
Key: ISIS-434
URL: https://issues.apache.org/jira/browse/ISIS-434
Project: Isis
Issue Type: New Feature
Affects Versions: viewer-wicket-1.2.0, core-1.2.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
works very similar to choices, eg:
Customer getCustomer() { ... }
ListCustomer autoCompleteCustomer(String searchArg) { ... }
--
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
[jira] [Updated] (ISIS-434) Provide context-specific autoComplete through prefixed methods on properties
[
https://issues.apache.org/jira/browse/ISIS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-434:
-
Component/s: Viewer: Wicket
Core
Provide context-specific autoComplete through prefixed methods on properties
Key: ISIS-434
URL: https://issues.apache.org/jira/browse/ISIS-434
Project: Isis
Issue Type: New Feature
Components: Core, Viewer: Wicket
Affects Versions: viewer-wicket-1.2.0, core-1.2.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
works very similar to choices, eg:
Customer getCustomer() { ... }
ListCustomer autoCompleteCustomer(String searchArg) { ... }
--
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
[jira] [Created] (ISIS-434) Provide context-specific autoComplete through prefixed methods on properties
Dan Haywood created ISIS-434: Summary: Provide context-specific autoComplete through prefixed methods on properties Key: ISIS-434 URL: https://issues.apache.org/jira/browse/ISIS-434 Project: Isis Issue Type: New Feature Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Updated] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-433: - Component/s: Viewer: Wicket Core Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Components: Core, Viewer: Wicket Affects Versions: viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Updated] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-433: - Fix Version/s: core-1.3.0 viewer-wicket-1.3.0 Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Components: Core, Viewer: Wicket Affects Versions: viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.3.0, core-1.3.0 works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Commented] (ISIS-434) Provide context-specific autoComplete through prefixed methods on properties
[
https://issues.apache.org/jira/browse/ISIS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679586#comment-13679586
]
ASF subversion and git services commented on ISIS-434:
--
Commit 8af98a50f093034e711b0c0f93a274b455fc7ef7 in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=8af98a5 ]
ISIS-434: autocomplete for properties
Provide context-specific autoComplete through prefixed methods on properties
Key: ISIS-434
URL: https://issues.apache.org/jira/browse/ISIS-434
Project: Isis
Issue Type: New Feature
Components: Core, Viewer: Wicket
Affects Versions: viewer-wicket-1.2.0, core-1.2.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: viewer-wicket-1.3.0, core-1.3.0
works very similar to choices, eg:
Customer getCustomer() { ... }
ListCustomer autoCompleteCustomer(String searchArg) { ... }
--
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
[jira] [Commented] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679587#comment-13679587 ] ASF subversion and git services commented on ISIS-433: -- Commit 1491507 from [~danhaywood] [ https://svn.apache.org/r1491507 ] ISIS-433, 434; also page on applying patches Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Components: Core, Viewer: Wicket Affects Versions: viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.3.0, core-1.3.0 works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Commented] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679589#comment-13679589 ] ASF subversion and git services commented on ISIS-433: -- Commit 1491510 from [~danhaywood] [ https://svn.apache.org/r1491510 ] ISIS-433, 434 Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Components: Core, Viewer: Wicket Affects Versions: viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.3.0, core-1.3.0 works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
[jira] [Resolved] (ISIS-434) Provide context-specific autoComplete through prefixed methods on properties
[
https://issues.apache.org/jira/browse/ISIS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-434.
--
Resolution: Fixed
Provide context-specific autoComplete through prefixed methods on properties
Key: ISIS-434
URL: https://issues.apache.org/jira/browse/ISIS-434
Project: Isis
Issue Type: New Feature
Components: Core, Viewer: Wicket
Affects Versions: viewer-wicket-1.2.0, core-1.2.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: viewer-wicket-1.3.0, core-1.3.0
works very similar to choices, eg:
Customer getCustomer() { ... }
ListCustomer autoCompleteCustomer(String searchArg) { ... }
--
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
[jira] [Commented] (ISIS-433) Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method).
[ https://issues.apache.org/jira/browse/ISIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679590#comment-13679590 ] ASF subversion and git services commented on ISIS-433: -- Commit 1491513 from [~danhaywood] [ https://svn.apache.org/r1491513 ] ISIS-433, 434 Provide context-specific autoComplete through prefixed methods on actions parameters (cf choices method). - Key: ISIS-433 URL: https://issues.apache.org/jira/browse/ISIS-433 Project: Isis Issue Type: New Feature Components: Core, Viewer: Wicket Affects Versions: viewer-wicket-1.2.0, core-1.2.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.3.0, core-1.3.0 works very similar to choices, eg: Customer foo() ListCustomer autoComplete0Foo(String searchArg) -- 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
Some new features for Wicket viewer in trunk
A few new features recently added to the Wicket viewer... 1. @SortedBy annotation, to allow different sort orders for parented collections (overriding to the natural sort order; applicable to SortedSet collections) [1], [2] 2. columns in Wicket viewer's tables are now sortable [3] 3. a new autoComplete prefix can be used (similar to choices), providing the ability to do context-specific autocompletes. [4],[5],[6],[7] Enjoy! Dan [1] https://issues.apache.org/jira/browse/ISIS-430 [2] http://isis.apache.org/applib-guide/reference/recognized-annotations/SortedBy.html [3] https://issues.apache.org/jira/browse/ISIS-432 [4] https://issues.apache.org/jira/browse/ISIS-433 [5] https://issues.apache.org/jira/browse/ISIS-434 [6] http://isis.apache.org/applib-guide/how-tos/how-to-03-025-How-to-specify-an-autocomplete-for-an-action-parameter.html [7] http://isis.apache.org/applib-guide/how-tos/how-to-03-015-How-to-specify-an-autocomplete-for-a-property.html
Re: Few Queries regarding the tests
On 10 June 2013 20:49, Bhargav Golla bhargav.go...@gmail.com wrote: 1. Delete_thenResponseCode_205_bad: Should I check for a DELETE request and then check for response code? Not sure what you mean by check for a DELETE request. You need to submit an HTTP DELETE in the client, and then assert in the client that you get a 205 response. There's a good chance, though, that this test will fail - ie that the server does not correctly implement this behaviour. You are very welcome to dig into it if so will probably involve some rooting around in RestEasy and the JAX-RS. However, if you get nowhere, then skip this test and find something easier to work on (at least, while you are coming up to speed). Such as... 2. Get_thenResponseHeaders_ContentLength_ok: What is the content length I should check for? With these, the easiest thing is to just assert on a nonsense value, have the test fail, and then (so long as you've manually verified that the response looks ok), take this content length as the one to check for. What we're after here is a regression test; there's no easy way - other than manual inspection - to figure out the initial value. For a slightly more robust test, you might want to check that the content length is larger than some value. After all, if there are changes it'll probably involve the addition of new members to the class; which would break this content length test. All we want is a reasonableness check here, ie yes, a content length was returned, and yes, it looks about right. Thx Dan
