How to connect VCR with DAY CRX

Question

Hi all,
we try to connect Day CRX as content repository in WLP 10.2. We followed the documentation in http://edocs.bea.com/wlp/docs102/pdf/day170adapter_developers_guide.pdf. This sounds very easy - but does not work. Entering the Connection Class "com.day.content.spi.jsr170.RMIRepository" while adding a new repository connection, we get an "Type of connection class is invalid" error.
Any ideas what's going wrong here?
Thanks in advance.

Answer 1

My guess is that this is the issue tracked with CR367383: "Validation in BrowseReposBaseController too strict - cannot connect old-style SPI implementation". There is an easy workaround but you can request a patch if you want to. Reference the CR if you open a support case for a patch.
This has been fixed in the next release. It is supposed to be in the release notes for 10.2, but I don't see it there. This is what it was supposed to say:
Title: CM: Unable to add repository config for some non-BEA repositories via WLP Admin Tools due to 'Class.isAssignable error'
Description:
The WLP Admin Tools currently do not allow one to create a repository configuration for certain non-BEA repositories which implement the old SPI
interface. However, this is not a CM limitation. If the repository configuration is manually created in the content-config.xml file, it will work as expected.
Platform: All
Workaround: If you are unable to create a repository configuration via the WLP Admin Tools, manually edit the application's META-INF/content-config.xml file and add a section like the following:
<content-store>
<name>myRepository</name>
<class-name>com.my.repository.class</class-name>
<repository-property>
<name>cm_fireRepositoryEvents</name>
<value>false</value>
</repository-property>
<read-only>false</read-only>
<search-is-enabled>true</search-is-enabled>
<fulltext-search-is-enabled>false</fulltext-search-is-enabled>
<search-indexing-is-enabled>false</search-indexing-is-enabled>
</content-store>
Then redeploy the application, and it should be visible via the WLP Admin tools.
Note that if you have a deployment plan, the domain configuration may override the content-config.xml configuration.