Hi paolomoz, thank you very much for your reply, and sorry for my late follow-op (i've been away).
So if I understand correctly, I will not be able to "register" a Jackrabbit CMIS source in Alfresco, and then access its content as if it was stored locally in Alfresco using existing Alfresco functionality.
However, I will be able to access LifeRay Jackrabbit content and display it in the separate Alfresco server if I write custom code for it on the Alfresco side. In my view this would put CMIS on the same architecture abstraction level as SQL.
This would still be an important improvement, as this remote access would not be possible without the JackRabbit CMIS support, right?
To make it clearer what kind of scenarios I was considering:
-We use Liferay/Jackrabbit to store content, but configure JackRabbit to actually store contents using CMIS on the Alfresco Server, completely transparent to the LifeRay portlets still using JSR 170 (transparent remote storage).
-We create custom portlets that use JSR 170 against JackRabbit, but the contents are actually retrieved from Alfresco (transparent remote access)
-Other "enterprise" clients only access Alfresco as a single content repository, even when content actually are stored across many repositories (aggregation).
Any thoughts are appreciated.
-Karl Ivar