Java - Alfresco

Alfresco Content models are defined in the Data Dictonary as meta-model. The meta-model consists of two main structures - Content Types and Content Aspect . Content Type is the fundamental Structure of a content item. It defines the composition of properties and behaviours of a content item. Much like in the object-oriented programming model where an object always has to be a defined class type, in Alfresco an item has to be a defined type also. Types are like types or classes in the object-oriented world. They can be used to model business objects, they have properties, and they can inherit from a parent type. “Content”, “Person”, and “Folder” are three important types defined out-of-the-box. There is a root content type defined in Alfresco, all other content types are created inheriting this root type - cm:content or {http://www.alfresco.org/model/content/1.0}content There are two parts in defining the name Namespace of the content type Name of the content type

1) Solr uses Lucene under the hood. Lucene has no clue about the Solr API. 2) Lucene is a powerful search engine framework that lets us add search capability to our application. It exposes an easy-to-use API while hiding all the search-related complex operations. Any application can use this library, not just Solr. 3) Solr is built around Lucene. It is not just an http-wrapper around Lucene but has been known to add more arsenal to Lucene . Solr is ready-to-use out of box. It is a web application that offers related infrastructure and a lot more features in addition to what Lucene offers. 4) Lucene doesn't just create the Index for the consumption by Solr . Lucene handles all the search related operations. Any application can use the Lucene framework. When to use Lucene? You are a search engineer AND You are a programmer AND You want full control over almost all the internals of Lucene AND Your requirements demand you to do all sorts of geeky customization to