cancel
Showing results for 
Search instead for 
Did you mean: 

Create new types ?

Rafael_Bueno
Confirmed Champ
Confirmed Champ

Is possible create new types using opencmis with the Nuxeo or just putting xsd with extensions and restarting the tomcat server ? Restart the server is a big problem for me.

http://chemistry.apache.org/java/opencmis.html

I also don´t want use the Nuxeo Studio for do that.

1 ACCEPTED ANSWER

rg1_
Star Contributor
Star Contributor

I believe document types can now be reliably hot deployed. It should not be too hard to modify nuxeo-chemistry to use the nuxeo-core SchemaManager to dynamically register new types. The challenge is persisting the new dynamically-registered types so that they get re-registered upon restart.

View answer in original post

8 REPLIES 8

rg1_
Star Contributor
Star Contributor

I believe document types can now be reliably hot deployed. It should not be too hard to modify nuxeo-chemistry to use the nuxeo-core SchemaManager to dynamically register new types. The challenge is persisting the new dynamically-registered types so that they get re-registered upon restart.

@rg1 I just want to confirm some steps

Florent_Guillau
World-Class Innovator
World-Class Innovator

Nuxeo can dynamically create new types (because that's actually what's used internally to create the types when Nuxeo starts), but we don't really support that because, as @rg1 said, there's no mechanism to persist them and take them into account at the next server restart. So even if we implement some optional CMIS 1.1 features, this won't be among them.

We don't have this feature because we haven't seen a demand for it. Creating types is usually done by expert people and rarely done in the life of the server. It needs testing and care.

If the need is to be able to add types to a server (basically upgrade the application) without service interruption, then Nuxeo in cluster mode (and restarting one node after the other) is the proper answer.

Florent, one caveat. I suspect forthcoming, off-the-shelf CMIS 1.1 apps may come with installers that want to dynamically register new types. These applications will not want to ship with custom configuration modules unique to each CMIS vendor.

Yes we've considered that, and it's a good way to solve the problem. Maybe not in the content repository but this remains to be determined. There has never been a pressing enough need to implement it though.

I agree with @rg1, some applications want to work like a HUB of DAMs, the CMIS Protocol make all repositories looks like a Database, so now is very easy to work that way. We dont want create a DAM or ECM, we just want use one and make the users from our application be free to choose the DAM they want. But CMIS 1.1 is kind recent, so @Florent Guillaume is right to.

@Florent Guillaume, you asked to put this information here, so here is

Nuxeo Studio is an external configuration tool that generates a full Nuxeo bundle (plugin). This bundle is then downloaded by Nuxeo, and seen on next Nuxeo restart (or hot-reload).

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.