A question for Pete and Berin - is is possible/reasonable to isolate instrumentation depedencies into a lifecycle extension handler? Just looking at the instrumentation doc pages it would appear so on an initial read - however the doc is more focussed on the client usage point of view as distict from the container perspective.
Should be absolutely no problem. Components which implement Instrumentable are designed to function correctly even if the container is not Instrument aware.
The only drawback with doing this is that several components of Fortress itself are currently instrumentable. It currently will instrument the lookup and releasing of components even if those components are not themselves instrumentable. In order for that to work, the instrument jars must always be available. If they are always available, then there is no reason to change Instrumentable to an extension lifecycle. Thoughts?
Leif
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
