That'd require manual configuration, potentially complicating the build
and/or deploy process, but that doesn't make it a bad idea. Grabbing it
from a JNDI resource would be another potential solution.
Not sure if it could be (reliably) automatic with scanning, either,
although perhaps there's alr
2012/5/31 Dave Newton :
> I think you'd have to either scan for a type or annotation; before the
> framework is up not sure what other options there could be.
Thanks Dave, but right now I think about something simpler like
specifying FileManager implementation's class as a context-param and
provid
