The tie into the jbossas server/deployer layer for this would be a
proper expression of the logging framework version dependency. This
should be possible with the new class loading layer. It would be nice if
an the logging version dependencies could be collected and a
DeploymentStage.DESCRIBE level class loader setup the api and
configuration mapping layers.
David M. Lloyd wrote:
Yeah, this is the exact basis of my idea to make emulation APIs for
AS/MC deployments. We could provide APIs for every logging framework
known to mankind, including multiple versions of the same framework if
they happen to be incompatible (if we do our deployments correctly
anyway).
Then the user just has to specify what logging API they use in their
deployment somehow (it would be cool if we could just dynamically
sniff out that info). As Scott pointed out, we also would need a way
to parse all the different logging config formats. Which pretty much
brings us up to date. :-)
- DML