5 Replies Latest reply on Jan 5, 2008 4:54 PM by Rob Stevens

    Items Broken with 3.1.3 -- tree component, table spacing, an

    Rob Stevens Newbie

      Tree component: A bug that was fixed has come back. When an item is removed from a tree by dragging, the tree is not re-rendered correctly. The list remains the same length, but one of the nodes is repeated. This worked correctly in 3.1.2 -- (PS thanks for taking out the "system.out.println" debug message -- that was annoying!! :) )

      The table cell spacing has changed. Used to be tighter -- have some style values changed? It is difficult to write code to a library that makes these changes unannounced.

      Bug 1099 is still there -- responsecomplete processing for components that extend AjaxActionComponent (e.g. MenuItem)

        • 1. Re: Items Broken with 3.1.3 -- tree component, table spacing
          Nick Belaevski Master

          Could you please provide some more info on these issues?

          1. Code of page & bean for tree component.
          2. As far as I know, none of style values should be changed or had changed. What component are you talking about: all table-based components or just a concrete one?
          3. 1099 is said to be reproduced on JSF 1.1 only. Are you using 1.1 version?

          • 2. Re: Items Broken with 3.1.3 -- tree component, table spacing
            Rob Stevens Newbie

            Thanks for the quick response.
            Let's deal with item #3 -- bug 1099 I'll do separate posts for the other issues.

            I'm using JSF 1.2 RI and Facelets

            It is pretty simple to reproduce the issue. Set up a series of menuItems --

            Make one of these items produce a PDF, Excel, or CSV file by writing directly to the servletoutputstream. End the method with a 'responseComplete' call. You should still be on the same page.

            Now when you select any of the other menuItems, the file will be extracted again before the new menuItem is envoked. This happens in 3.1.2 and 3.13

            • 3. Re: Items Broken with 3.1.3 -- tree component, table spacing
              Nick Belaevski Master

              Thank you, we'll check! Reopened the issue...

              • 4. Re: Items Broken with 3.1.3 -- tree component, table spacing
                Rob Stevens Newbie

                The second problem I reported, table column widths, appears to be somewhere in the HTMLColumn component. Each column is getting a width of 100px -- don't know where that is coming from. I never requested it.

                Is this a problem with the component?

                As to the first problem, the tree component. All you need to do to show this problem is to create a tree with a few items. Use D&D to remove an item and notice how the list will re-render to the same length. The newly deleted item will not be there, one of the old ones will be repeated.

                For example -- before delete

                Item 1
                Item 2
                Item 3
                Item 4

                Then use D&N to remove item 3 the list will re-render as:

                Item 1
                Item 2
                Item 4
                Item 4

                This worked correctly in 3.1.2

                • 5. Re: Items Broken with 3.1.3 -- tree component, table spacing
                  Rob Stevens Newbie

                  The second problem I reported, table column widths, appears to be somewhere in the HTMLColumn component. Each column is getting a width of 100px -- don't know where that is coming from. I never requested it.

                  Is this a problem with the component?

                  As to the first problem, the tree component. All you need to do to show this problem is to create a tree with a few items. Use D&D to remove an item and notice how the list will re-render to the same length. The newly deleted item will not be there, one of the old ones will be repeated.

                  For example -- before delete

                  Item 1
                  Item 2
                  Item 3
                  Item 4

                  Then use D&N to remove item 3 the list will re-render as:

                  Item 1
                  Item 2
                  Item 4
                  Item 4

                  This worked correctly in 3.1.2