title: How can I decouple a non-Spring client from the configuration of a Spring-based jar?
body: <p>I have only limited experience with Spring but am working with someone who really likes it.  We've built a set of packages that use Spring heavily and now we need to provide an access layer that exposes that functionality to clients that may not use Spring.</p>
  
  <p>My primary goal is that clients of the access layer should not be required to configure Spring in order to use it.  Obviously Spring will be on the deployment classpath.  In an ideal world, the client could build against the access layer package and deploy without knowing that Spring is being used.  Is this possible?  (No, using a remote service is not an option.)</p>