[jira] [Commented] (OFBIZ-644) Pagination in https://host_name:8443/ordermgr/control/orderlist needed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-644) Pagination in https://host_name:8443/ordermgr/control/orderlist needed

Nicolas Malin (Jira)

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

Adrian Crum commented on OFBIZ-644:
-----------------------------------

I just wanted to comment that David's analysis of this design approach was correct and his prediction about this change came true.

If I want to set up default selections by passing URL parameters to this screen, they are ignored because of the behavior of the Java class. Also, since the class is stored in the session, multiple browser tabs pointing to the same screen interfere with each other. In other words, this change created quirky screen behavior and it is difficult to troubleshoot.

From my perspective, this code should not have been committed.

               

> Pagination in https://host_name:8443/ordermgr/control/orderlist needed
> ----------------------------------------------------------------------
>
>                 Key: OFBIZ-644
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-644
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: order
>    Affects Versions: SVN trunk
>         Environment: All
>            Reporter: Walter Vaughan
>            Assignee: Jacques Le Roux
>             Fix For: SVN trunk
>
>         Attachments: orderliststate-svn.patch, orderliststate.patch
>
>
> There is no pagination in https://host_name:8443/ordermgr/control/orderlist. If a status like "sent' is chosen, thousands or millions of rows will be returned if there is that many in the database. Some sort of pagination system like we have in https://host_name:8443/partymgr/control/findparty with some sort of higher limit like 100 records or so might be good, as to not break behavior for most existing users.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira