A volume-transition can not be present at the beginning and end of the same page

[bertfrees]

For example, a any-resumed will never be rendered at the start of a volume of only one page, because any-interrupted (which may be empty) will always win in that case.

This is clearly very unlikely to happen in a real situation. However it would still be good to support it, or at least notify the user of it with a warning message. In a testing scenario it is not so unlikely that a volume has one page. It happened to me and I spent a lot of time chasing what I thought was a bug somewhere else in the code.

To fix it properly is not so difficult, but there is also a solution in between that is even simpler, namely to let any-resumed win in case of conflicts when any-interrupted is empty. Then you can still not test them together on the same page, but at least you can test one or the other.

[bertfrees]

This was my temporary solution to make my test work:

@@ -333,7 +333,11 @@ public class SheetDataSource implements SplitPointDataSource<Sheet, SheetDataSou
                             }
                         }
                         volumeEnded = transition != null;
-                    } else if (sheetBuffer.size() == 0 && (!sectionProperties.duplex() || pageIndex % 2 == 0)) {
+                    }
+                    if (sheetBuffer.size() == 0 && (!sectionProperties.duplex() || pageIndex % 2 == 0)
+                        && (transition == null || (transition.getInAny().isEmpty()
+                                                   && transition.getInSequence().isEmpty()
+                                                   && transition.getInBlock().isEmpty()))) {
                         transition = context.getTransitionBuilder().getResumeTransition();
                     }
                 }