Community
Participate
Working Groups
The order in which the adaptable scope is switched to the different viewers decides which ContentPartPool is injected into the ContentBehaviors of the content parts contained within the respective viewer. While different ContentPartPools are injected into the root parts of the different viewers, only the ContentPartPool of the viewer to which the adaptable scope was most recently switched to is injected into the visual parts of all viewers. This could be solved by injecting the ContentPartPool as an adapter into the root part, instead of using Guice member injection to directly inject it into ContentBehavior.
I changed the ContentPartPool to extend IAdaptable.Bound.Impl<IRootPart<? extends Node>>, changed the bindings within MvcFxModule accordingly, and updated the ContentBehavior to query the ContentPartPool from the IRootPart of its host. The code is published on the master branch, therefore, I resolve this ticket as fixed for 5.0.0 M3.