Provide a lightweight / safer contribution model

In the context of PaaS architecture like nuxeo.io, this could make sense to have a safer way to contribute code to a Nuxeo server.

By Safer we mean :

• safer for the Nuxeo Server : restrict power of the code
• safer for the underlying Server infrastructure

This could include :

a dedicated Configuration :

For example, have restrictions on running Operations via Http

• filter out Operations that can execute Script
• filter out Operations that can access the FileSystem
• filter out Operations that can do ShellExec

new ways to contribute code

If we allow direct Java contribution, we can only rely on container isolation.

To make this easier and safer, we may provide a first level of extension that allows to contribute scripting (JavaScript or Groovy) rather than Java code.

We already have something like that for Listeners and Operations, we should :

• normalize that with a restricted script execution engine
• extend that to Seam Beans ?
• extend that to Work ?