This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | JSF Application Developement | ||
---|---|---|---|
Product: | obsolete | Reporter: | manuellp12 <manuellp12> |
Component: | visualweb | Assignee: | issues@obsolete <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | pzavadsky, quynguyen, wjprakash |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
manuellp12
2008-03-04 15:19:01 UTC
Hi, thanks for the feedback. This one includes a lot of independent issues which span more modules. Let me get this point by point: 1) That are the memory leaks, which should be fixed now (in 6.1), CC'ing Quy. 2) The same as 1) 3) The corruption belongs to insync or components; a case is needed (please provide log file or exception stack as a minimum), CC'ing Sandip and Winston. 4) That should be a consequence of the memory leaks (same as 1) and 2). 5) I just tried the centering (in 6.1) and it works there. It might have been fixed after 6.0, or if you have another case, please, provide it, CC'ing myself. Please, clarify about the selectable table. It sounds to me it belongs to the components (in case you ask for certain property to be available) - Winston; 6) This I am not sure where it belongs to, JSP editor, refactoring, insync? 7) This might be one part the memory leaks, and other is unfortunately inherent because of the architecture used. We are trying to solve it in some future release. 8) That belongs to JSP editor, web/jspeditor; I evaluated the designer problems (part of 5) and 7). Passing now to Quy to evaluate the memory leaks stuff. Then please, pass to the other guys. Many of the common IDE memory leaks have been fixed in NB 6.1. This includes a number of memory leaks during deployment. See Issue 123530 for details. There was no response long, time, I assume, the fixes in later releases satisfied the problem. Closing. Hi, sorry for the delay. The new releases of netbeans has solved many of these problems, but i hadn't the chance to make a full test, later i'll post the results. Well, about the item number 5, i'll explain how it would be really nice to have a selectable table. At this moment, natively, the jsf table is kind of static, however it can be made selectable, and the process is as follows: You create a table, then you insert a radio button or check box, depending of what you need. After this, you have to implement an interface to receive events from the table. And finally, you have to make some manual bindings, and after that, the table is selectable. As you see, this process consumes some time while the developer makes all these steps, every time a selectable table is needed, what is very often, and because of that, this represents a decrease in productivity. What i propose about this is a way to make it easier to make a table selectable. Remember the behavior of a JTable in JSE. This table model allows row and column selection natively, and is also possible to disable the selectable feature. Just with a minor variable configuration, through a 'set' method or a simple method override, you can switch between a selectable table behavior to a non selectable table behavior. This is what i suggest a JSF table to support, a variable configuration to enable a selectable behavior (either for multiple as for single selection), and avoid all the current steps you have to make to enable this. Basically, enable a table.setSelectable(multiple or single) and a table.getSelectedRow() for single selection and table.getSelectedRows() for multiple selection, methods to make this usage much easier. Thanks. OK, thanks for the response. So at this moment this boiled down to the need of selectable table jsf component (see previous comment). Passing to components to evaluate. Ok, thanks. What Visual JSF framework comes with is a set of components from Project Woodstock and doesn't have any component library of its own . So this is not a defect but a feature request for Project Woodstock. You can also file an enhancement against JSF RI to provide such a feature in standard JSF table. The other approach is for you to write your own custom component extending the APIs exposed by JSF if existing component libraries out there don't satisfy your needs. Sorry for not being to help you this regard. Thanks |