Community
Participate
Working Groups
Currently we create multiple part services: one for the "application" (in the workbench context), one in each trimmed window. The contexts also get part service creation function and most part contexts will have a cached pointer to the containing window's part service. That by itself would be not perfect, but bearable. However, multiple part services interact with each other in strange ways thanks to active*/selection* changes. That provides puzzling effects including recursive calls and changes spilling into "other" part services. I think we need to have single part service implementation residing at the application context. The services provided by the part service will be scoped "per application". (Currently they are scoped either "per window" or "per application" depending on where the implementation is taken from.) The change will mean that multi-window JUnit tests we have would need to be removed or updated, but it should not affect how SDK works.
(In reply to comment #0) > The change will mean that multi-window JUnit tests we have would need to be > removed or updated, but it should not affect how SDK works. That is "multi-window JUnit tests" that test the part service.
This matter has been discussed about in the past in bug 322428. Bug 322428 comment 6 and down in particular is of interest.
(In reply to comment #2) > This matter has been discussed about in the past in bug 322428. Bug 322428 > comment 6 and down in particular is of interest. Thank you! I could not find that one. *** This bug has been marked as a duplicate of bug 322428 ***
