[
http://jira.codehaus.org/browse/DISPL-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229187#action_229187
]
Blaine Simpson commented on DISPL-320:
--------------------------------------
The "Fix Version/s" field, and perhaps Status of this ticket seem to be wrong.
You can see at
http://displaytag.homeip.net/displaytag-examples-1.2/example-grouping.jsp that
higher groups are indeed re-displaying when only the lower group changes. This
example (example-grouping.jsp) unfortunately does not show lower groups
changing without the higher group re-displaying, but I have tested this myself
with 1.2 and that works too.
(When I say "higher" group here, I mean the col. with the higher "group" value
magnitude; not "higher" in a more intuitive "nesting" aspect. Higher groups
under this stipulation are MORE nested = are at a LOWER/deeper nesting level.)
I don't know whether it is also fixed in 1.1.1 or not, but that doesn't look
hopeful based on previous comments to this ticket.
> Multiple group levels on column are broken
> ------------------------------------------
>
> Key: DISPL-320
> URL: http://jira.codehaus.org/browse/DISPL-320
> Project: DisplayTag
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Jeff Sheets
> Fix For: 1.3
>
> Attachments: differ and test files.rar, diffResults.txt,
> TableWriterTemplate-aynalem.java, TableWriterTemplate.java
>
>
> We have recently upgraded from 1.0 to 1.1 version of displaytag. Previously
> we could define column1 with group="1" and column2 with group="2" so that our
> grouping would have levels. When column1 changed groupings it would cause
> column2 to change, column2 could have multiple groupings for each group in
> column1.
> This is better explained in the displaytag reference doc for group:
> "The grouping level (starting at 1 and incrementing) of this column
> (indicates if successive contain the same values, then they should not be
> displayed). The level indicates that if a lower level no longer matches, then
> the matching for this higher level should start over as well. If this
> attribute is not included, then no grouping is performed."
> This behavior is broken in 1.1, as the levels are not respected. col2 is
> grouping even when col1 is not. Here is an attempt at an example:
> Correct 1.0 behavior:
> Col1 (group="1") Col2 (group="2")
> Omaha 50
> Omaha (50 here is hidden by grouping)
> Omaha 23
> Omaha 22
> Chicago 22 (22 here is shown because col1 changed
> values)
> Chicago (22 here is hidden by grouping)
> Chicago 42
> Chicago 43
> Incorrect behavior occurring in displaytag 1.1:
> Col1 (group="1") Col2 (group="2")
> Omaha 50
> Omaha (50 here is hidden by grouping)
> Omaha 23
> Omaha 22
> Chicago (22 here is incorrectly hidden even
> though col1 changed values)
> Chicago (22 here is hidden by grouping)
> Chicago 42
> Chicago 43
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
displaytag-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
