Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/718
scratch the `ClassLoadingContext` suggestion: it's hard, and I've come to
the conclusion it's misguided. it serves a different, narrower purpose than a
resulting instance's search path (where ancestors probably are wanted), but in
short it makes sense to defer that "ancestor-bundles-are-transitively-visible"
decision to the instantiation engine (which might want to hide it) rather than
mandate it as part of the CLC for an item. aside from `EntitySpec` we don't
have a strong use case for supertype bundles being visible at the type: the
instantiation engines don't need them (apart from XML deserialization which is
ugly).
also to do it properly i now think (after a reverted attempt included here
in case we change our minds!) means making actual supertypes part of the type
API, which is a sensible thing to do (and the existing
`RegisteredType.getSupertypes()` is hokey) but requires a more sophisticated
initialization (because currently we don't attempt to parse and discover
supertypes until instances are used). it's overkill to do that just for the
problem we're solving here!
comments to this effect in the last commit,
https://github.com/apache/brooklyn-server/pull/718/commits/3b39ca65d1b871506a2dd61f6790fc1bd2473472
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
