There's a bit of complexity down inside the service architecture for dealing with different bean containers, and apparently even with multiple bean containers being used concurrently. DSpaceServiceManager keeps a list of ServiceManager instances and asks each one if it offers a given service.
It's very nicely done. But do we need it? There are mutterings about using Guice, but I don't recall ever hearing of anyone working on doing it. There is, so far as I can tell, one actual ServiceManager implementation: SpringServiceManager. And though I can't point to specific places offhand, I recall seeing code elsewhere which appears to assume that Spring is present. And (selfish motive exposed!) I would be able to make good use of SpringServiceManager.getBeanFactory if I could get at the SpringServiceManager instance that is running. (See my earlier query about bean access and unit testing.) The service architecture has been out there for some time now. Should we declare Spring the victor and do some consolidation? -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgpdm7Uxe4dsK.pgp
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
