Brian Stansberry wrote:
So, yeah, using <cluster/> as a trigger to add some extra capabilities sounds good.
Yeah, that's the goal or at least the direction i would like to go. I would like to look at some more use cases to see what's really needed and if this can be handled in a better way. In the end ProfileService is limited in what it can/should do - so it's the combination of module requirements (deploy only what's needed), on-demand beans (start only what's needed) and something like your on demand profile activation which needs to make sense altogether.