Accessing same Content Management Repository from Multiple Domains

Question

I'm attempting to point many different domains to a single content management repository to avoid the duplication of data.
All the domains are able to read content correctly, but when trying to create content (whether programmatically or through the admin tool), most of the domains will get this error:
java.sql.SQLException: ORA-00001: unique constraint (SCHEMA_NAME.PK_CM_NODE) violated
Since there's no sequence generated in the database, it appears that the primary key is defined by something in the portal code. This seems to imply that you can't have multiple domains pointing to the same repository. Can someone confirm that they've seen this work? And if you've gotten it to work, what I am doing wrong?
Thanks for any help,
Dan Turkenkopf

Answer 1

This particular issue is inherent to the OOTB repository in WLP. The repository uses a sequencer to generate id's for created content. The way these ID's are generated causes the possibility of two applications attempting to create items with the same ID. This is due to the fact that the WLP repository manages the ID's used when creating content and doesn't currently use a GUID strategy for content id's.
You could configure another repository which does ID generation in a different fashion and avoid the persistence problem I've described.
The VCR layer which provides the access to the OOTB repository really only has the cache issue I described. This can be worked around with some custom event listener implementations that can manage stales caches. These would need to be aware of the other applications sharing the underlying content repository.
-Ryan