Community
Participate
Working Groups
With the patch for bug 358714 we now have support for parallel resource loading. This is however not enabled by default, as the implementation would not be able to deal with resources which dynamically load other resources as part of the load phase (see bug 358714 comment #27). It would be good if we could devise a strategy to deal with this problem and could then enable the parallel resource loading by default.
One problem I've encountered with the current ParallelResourceLoader implementation is that the individual loader's ResourceSets will "inherit" the ResourceDescriptionsProvider.NAMED_BUILDER_SCOPE load option without having the corresponding adapter set. This will lead to problems if a resource does try to access the index during loading.
A possible solution to deal with resources which load others during the load phase could be to explicitly unload those other resources again before returning the primary loaded resource. This should correctly proxify any references it has to the other resources.