anchor.diff:  Content repositories can therefore optionally be made searchable by extending the `Searchable<CID>` interface.
   
   [source, java]
  ++
   .Searchable interface
   ----
   public interface Searchable<CID> {
  
positive.code: Content repositories can therefore optionally also be given rendition capabilities by extending the `Renderable<E>` interface.
  
  [source, java]
  .Renderable interface
  ====
  public interface Renderable<E> {
  
  	InputStream getRendition(E entity, String mimeType);    <1>
  }
  ----
  <1> Returns a `mimeType` rendition of the content associated with `entity`
  ====
  
  [[content-repositories.creation]]
  == Creating Content Repositories Instances
  
negative.code: . Inject the repositories and use them
  +
  [source, java]
  ----
  public class SomeClass {
  	@Autowired private SopDocumentRepository repo;
    	@Autowired private SopDocumentContentRepository contentRepo;
  
  	public void doSomething() {
  		SopDocument doc = new SopDocument();
  		doc.setTitle("example");
  		contentRepo.setContent(doc, new ByteArrayInputStream("some example content".getBytes()));
  		doc.save(); 
  		...
  		InputStream content = repository.getContent(sopDocument);
  	}
  }
  ----
  - Spring Content will update the `@ContentId` and `@ContentLength` fields
  