On Feb 14, 2011, at 6:27 PM, Brian Stansberry wrote:
Let's assume for the sake of argument that we want to expose
dependency
info via the management interface. I see here hard dependencies (e.g.
presumably JCA and JTA) and optional. Extensions could register these
dependencies when they initialize. It opens up a can of worms though, as
we'd need a proper language to describe the dependencies.
Thinking out loud here, could we use the module dependency information
for this? Nah, that would just say, e.g. that JCA needs the JTA APIs,
but says nothing about the impl.
As I said in an earlier email. To me, this is edge case that can easily be considered
something that we don't support. If we need or want todo it, it needs to be fool
proof
and hence require a way to describe these dependencies and to validate newly created
profiles.
Furthermore, if it's not a strict requirement, we drop this idea.
Ike