- RM: Nuxeo provides a model for structured schema-based data (what they call "content objects" or "documents"). The following features are inherent and integrated parts of Nuxeo "content objects":
- versioning support
- a simple and fine grain caching model (includes lazy loading features)
- support for indexing and searching (storage independent query language)
- state management ("life cycle") management
- support for workflow around "content objects"
- event triggers and rule engine support (for managing business behaviors/models) on "content objects"
- RM: Nuxeo provides a default security (auth-n and auth-z) model and implementation.
- RM: OSGi support for RCP like Eclipse
- RM: Much of the developer documentation is often awkwardly written and sometimes difficult to understand.
- RM: There appears to be few (if any) projects that are using Nuxeo Platform in a manner similar to how the CollectionSpace Services team expects to use it.
- RM: Nuxeo Core API requires/uses EJB3 -this can be a blessing or a curse depending on our specific implementation of the services.
- SD: Multi-tenancy: Like any other typcial enterprise software, Nuxeo is not built ground up keeping multi-tenant deployment in consideration. We have listed issues and concerns regarding supporting multi-tenancy as listed below.
QUERY LANGUAGE INVESTIGATION
- As of release 5.2, Nuxeo's query API (NXQL) does not support search for complex schema types. Unfortunately, this means to use NXQL, all of our schemas need to be "flat."
Follow the instructions provided on the "How to" page.