我对CMIS主题还是个新手，我仍在搜索了解，我想做的是创建一个Java客户端，将报告上传到任何支持“CMIS”的内容管理v1.0 OASIS 标准规范”。 例如 Alfresco 、 Documentum 或 Microsoft SharePoint Server 我发现 opencMIS< /代码> 对于Java 是一个不错的选择..
但我仍然对编写此类应用程序与这些 CMS 和存储库进行通信所需的内容感到有点困惑。
- 我需要单独处理每一个，还是创建一次就可以了
会处理任何支持该标准的 CMS 吗？
- CMIS 客户端如何连接到基于 CMIS 的服务器。我们是否会有身份验证数据和通信端点（URL）？
- 如果可能的话，请简要说明一下，使用 OpenCMIS 制作 CMIS 客户端需要执行哪些步骤，对于没有任何此主题经验且了解 xml、http 等知识的人来说，这是否是一项艰苦的工作？
提前致谢
I am still new in CMIS subject , and I am still searching learn about that, What I want to do is to create a Java client that upload report to any content management that support "The CMIS v1.0 OASIS Standard Specification". such as Alfresco , Documentum or Microsoft SharePoint Server I found that opencMIS for Java is a good choice ..
But I am still a bit confused about what is required to write such application the communicate with these CMSs ans repositories .
- Do I need to handle each one alone , or to create it once and it
will deal with any CMSs that support this standards ?
- How the CMIS client will connect to the CMIS-based server. Do we will have authentication data and a communcation endpoint(URL)?
- Please if possible-briefly- what are the steps required to do to make a CMIS client using OpenCMIS, does it a hard work for who don't have any previous experience in this topic on has a knowledge about xml, http ..etc?
Thanks in advance
发布评论
评论（1）
OpenCMIS 确实可以让您从低级协议详细信息（例如 XML 有效负载）中抽象出来等等。另一方面，强烈建议掌握 协议本身，只是为了在设计应用程序时知道什么是可能的，什么是不可能的。
此外，CMIS 背后的想法是同一个库可以访问所有兼容的 CMS，而无需更改任何代码。现实情况是，供应商可能拥有可能无法完全移植的特定扩展，并且您的应用程序可能需要重新设计以支持新的 CMS (露天方面就是一个很好的例子）。
由 页面 /users/313137/romain-hippeau">@Romain Hippeau 提供了许多 OpenCMIS 客户端 API 使用示例。
OpenCMIS is really there to let you abstract from the low level protocol details such as XML payloads and the like. On the other hand, it's highly advisable to get a grasp of the protocol itself, just to know what's possible and what not, when designing your application.
Also, the idea behind CMIS is that the same library can access all the compliant CMSs without any code change. What happens in reality is that vendors might have specific extensions that might not be fully portable, and your application might need reworking to support a new CMS (Alfresco aspects are a good example).
The page linked by @Romain Hippeau is providing a number of examples of the OpenCMIS client API usage.