-
1. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
Can you be a bit more specific about what isn't working ?
ModeShape's CMIS support is built upon Apache Chemistry 0.11 which should have support for CMIS 1.1
-
2. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
I have the "ModeShape subsystem for Wildfly 10.x and 9.x" on wildfly 10 deployed
As far as I could see, the file "CMISWS-Service.wsdl" in the "modeshape-cmis.war" is configured for CMIS 1.0 support.
We need CMIS 1.1
So my questions are:
- how to configure modeshape for CMIS 1.1
- what is the easiest way to do that
Thank you in advance.
-
3. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
As far as I could see, the file "CMISWS-Service.wsdl" in the "modeshape-cmis.war" is configured for CMIS 1.0 support.
if you look inside the web.xml file you should see the servlet mappings both for CMIS 1.0 and CMIS 1.1. So using the URL <host>/modeshape-cmis/services11/cmis?wsdl should give you the WSDL for 1.1
-
4. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
Thank you for your answer.
I did following:
- I edited the "cmis11/CMISWS-Service.wsdl.template" , renamed it and copied it to the folder "wsdl/CMISWS-Service.wsdl".
- The "web.xml" is configured as you described it in your example. (Is it correct that " CmisWebServicesServlet" is used for "1.0" and "1.1" ???)
- I did some test using "RestClient", wenn I connect to the "/atom11" the I get information about repository and version supported.
Below is the repository info, that I get wen using "atom11" and as you can see, the supported version is "1.0".
I tested also with Alfresco demo installation, and there is supported version "1.1"
<cmisra:repositoryInfo>
<cmis:repositoryId>XXXX</cmis:repositoryId><cmis:repositoryName>ModeShape</cmis:repositoryName>
<cmis:repositoryDescription> jcr.repository.name=ModeShape option.versioning.supported=true option.query.sql.supported=true node.type.management.multivalued.properties.supported=true node.type.management.overrides.supported=true level.1.supported=true jcr.specification.version=2.0 node.type.management.update.in.use.suported=true query.full.text.search.supported=true option.lifecycle.supported=false option.node.and.property.with.same.name.supported=true option.retention.supported=false option.node.type.management.supported=true identifier.stability=identifier.stability.indefinite.duration option.simple.versioning.supported=false query.stored.queries.supported=true node.type.management.orderable.child.nodes.supported=true jcr.specification.name=Content Repository for Java Technology API option.unfiled.content.supported=false option.baselines.supported=false node.type.management.primary.item.name.supported=true level.2.supported=true option.activities.supported=false node.type.management.multiple.binary.properties.supported=true query.languages=null option.transactions.supported=true option.locking.supported=true custom.rep.workspace.names=null query.xpath.pos.index=false option.update.mixin.node.types.supported=true query.joins=query.joins.inner.outer option.update.primary.node.type.supported=true jcr.repository.version=5.1.0.Final option.journaled.observation.supported=false option.access.control.supported=true node.type.management.value.constraints.supported=true option.shareable.nodes.supported=true custom.rep.name=XXXXoption.workspace.management.supported=true write.supported=true query.xpath.doc.order=false node.type.management.autocreated.definitions.supported=true option.observation.supported=true node.type.management.residual.definitions.supported=true jcr.repository.vendor=JBoss, a division of Red Hat option.xml.export.supported=true node.type.management.property.types=true node.type.management.inheritance=node.type.management.inheritance.multiple option.xml.import.supported=true node.type.management.same.name.siblings.supported=true jcr.repository.vendor.url=http://www.modeshape.org</cmis:repositoryDescription><cmis:vendorName>OpenCMIS</cmis:vendorName>
<cmis:productName>OpenCMIS JCR</cmis:productName>
<cmis:productVersion>0.3</cmis:productVersion>
<cmis:rootFolderId>[root]</cmis:rootFolderId>
<cmis:capabilities> <cmis:cmisVersionSupported>1.0</cmis:cmisVersionSupported>
<cmis:thinClientURI/>
</cmisra:repositoryInfo>
-
5. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
Those values (and files) are coming from OpenCMIS (not ModeShape), so if you still have problems with 1.1, maybe it's worth asking the OpenCMIS/Apache Chemistry community. However, I would first try some actual requests (either atom or SOAP) and check the actual 1.1 functionality.
-
6. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
Hi, thank you for your answer.
We tested with CMIS Workbench and it also returns CMIS version 1.0
Before I ask the team from Apache, could you confirm that ModeShape 5.1 repository supports CMIS 1.1?
I mean has anybody test it if it really works?
I ask you because we did some research and it seams that the Servlet init parameters are not passed to the Servlet, in the modeshape-cmis.war. Although we sett the WSDL to templates of CMIS 1.1 and in the "web.xml" is the CMIS 1.1 initialized.
Thank you in advance.
-
7. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
As I already mentioned in my first reply of this thread, ModeShape uses OpenCMIS 0.11. It doesn't add or remove any feature other than what the Apache libraries provide.
-
8. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
Hi Horia,
CMIS 1.1 works ! I did not find any forums of CMIS, but did it my self.
In the constructor of "org.modeshape.cmis.RepositoryInfoLocal" I added the following code:
#####################################
public RepositoryInfoLocal( String id,
RepositoryInfo info ) {
super(info);
this.id = id;
super.setCmisVersion(CmisVersion.CMIS_1_1);
super.setCmisVersionSupported("1.1");
}
###################################
What I've seen in the code, the different version of CMIS libraries are used, "11" and "12" !
The implementation of CMIS seems to be not quite ok in "org.modeshape.cmis" because in the CMIS Workbench you can see that some CMIS properties are not returned from modeshape.
Modeshape is super, the only problem is that CMIS is not stable.
Ist it possible to get new version of modeshape WEB applications?
Thank you in advance.
-
9. Re: CMIS Workbench connection with "services11" doesn't work! Does anybody has information how to configure "modeshape-cmis.war" in order to get CMIS 1.1 connection? Thank you in advance.
I'm not sure I understand: the RepositoryInfo is not changed or overwritten by ModeShape, but instead returned from OpenCMIS's base class: chemistry-opencmis/JcrRepository.java at chemistry-opencmis-0.11.0 · apache/chemistry-opencmis · GitHub
So if OpenCMIS supports 1.1 and above, shouldn't this be fixed in the OpenCMIS codebase ? Functionality wise, ModeShape does not change anything from OpenCMIS so I'm not sure I agree that ModeShape should "advertise" another CMIS version than what's coming from the base classes.