| Summary: | Call of combo.setItems terminates the session | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | juergen.panser |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ivan, jon |
| Version: | 1.5 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
juergen.panser
Juergen, Combo is not designed to manage such amount of items. Probably, JFace content assist (ContentProposalAdapter) is the correct class to use. Nevertheless, if this code worked in RAP 1.5M4 but not in RAP 1.5M5 we will investigate it. Actually this is a Jetty warning and Jetty terminate the session. You could increase the default value of 1000 by setting a system property (VM argument) -Dorg.eclipse.jetty.server.Request.maxFormKeys=5000 for example. In any case, using a Combo with a such amount of items will definitely make your application unusable slow/unresponsive in all browsers. As this is a Jetty behavior and you can control the maxFormKeys with a system property (see comment#2) I will close this bug as WONTFIX. To my opinion you are right: 2500 items in a combo are a nightmare. But that was a wish from our customer. He wants to see all attributes he can use in a inventory search. I will try the VM argument. Thanks. (In reply to comment #4) > I will try the VM argument. Thanks. This is will only be the first hurdle. If you really manage to put 2500 items in a Combo, this will ruin the performance. If you need to display all these items in a list, use a virtual Table instead, if needed you can put it in a drop-down shell. As an alternative, you could try the content assist API in JFace. Thanks for the suggestion, but the virtul table is too buggy. (In reply to comment #6) > Thanks for the suggestion, but the virtul table is too buggy. Virtual table is too buggy??!! This is something new for as. Could you explain what is buggy in the virtual Table? Can you give as examples? Even better - open a bug reports. For the virtual table see bug 338696 (In reply to comment #8) > For the virtual table see bug 338696 Juergen, this is only a single issue. If you search bugzilla for "virtual", you will see that there are only two bugs related to the virtual table. Sorry, but I can't say that a component is "too buggy" with only one or two known bugs. *** Bug 388796 has been marked as a duplicate of this bug. *** |