-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UP-4964: Fix configuration of BranchingRenderingPipeline on uP5 #1050
Conversation
…ipelineTerminatorTest.java, FocusedOnOnePortletPredicateTest.java, and ProfileFNamePredicateTest.java into the uPortal-rendering module (where they belong)
…figuration.java (XML to Java style)
… java.util.function.Predicate (Java 8 native)
…chPoint to make it easier to configure these (existing) capabilities in the uP5 way
…ingPipelineConfiguration
AppVeyor is failing due to unrelated issue from https://issues.jasig.org/browse/UP-4965 |
private IPortalRenderingPipeline alternatePipe; | ||
|
||
public void setOrder(int order) { | ||
this.order = order; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ what happens if two branch points have the same order
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One of them (randomly selected) will be processed first. IMHO that's fine. The alternative would be detecting the circumstance and throwing an exception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps logging a warning is a good middle ground.
…ain SemVer; check for multiple RenderingPipelineBranchPoint with the same 'order' value and throw an exception in case of collision
…ing features impacted by this fix
I removed the |
https://issues.jasig.org/browse/UP-4964
Checklist
Description of change
The configuration patterns we adopted for uP5 are a big improvement. Nevertheless, some uPortal capabilities are not yet manageable in the uP5 way. One such capability is uPortal Rendering Pipeline customization based on branching. This PR aims to address this bug -- to make it possible to configure branching pipeline settings properly in uPortal-start.
I intend to add documentation for these features before removing the
[WIP]
tag.