Getting the Lab 3 CMIS preview running

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

onewnan

Am seeking to kick the tires on CMIS ATOM and WS.  Installed the lab 3 server, and from svn the latest SDK plus Remote API project and dependies (from Elipse's perspective).   SDK FirstWebService executes OK (yes, that's the old style WS, but helps to verify proper configuration).  Eclipse reports no compile time errors with Remote API.

However, attempts to run CMIS unit tests (e.g., DMObjectServicePortTest) result in errors of the form:

"org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'luceneFullTextSearchIndexer' defined in class path resource [alfresco/core-services-context.xml]: Cannot resolve reference to bean 'indexerAndSearcherFactory' while setting bean property 'indexerAndSearcherFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'indexerAndSearcherFactory'  …"

I imagine what is happening is that Spring is trying to load these things dynamically and not finding them on the class path.  I tried importing the exploded EAR libs and also SDK Alfresco Remote–but neither solved the problem.  Any suggestions?

onewnan

These notes may be helpful to others who want to run Remote-API unit tests but, like myself, haven’t previously attempted Alfresco build and configuration starting from the svn repository.

If checking out less than the full sources, be aware that build scripts expect that all projects be within a directory called “projects”.  The root directory above that must furthermore contain the global (root) build scripts and resources.

The unerlying cause of the Spring BeanCreationExceptions  I reported turns out to be absence of a JIXB binding.   This can be created by running build.xml in the Repository project.   However, getting that to run properly requires modifiying build.properties in the global root directory to reflect current third party project naming:

#dir.project.3rdparty=${dir.projects}/3rd-party
dir.project.3rdparty=${dir.projects}/3rd Party

The CMIS unit tests also require repository database to be configured.  One might for example modify build.properties in the global root directory to point to the stand-alone server repository

#dir.root=./alf_data
dir.root=c:/Alfresco/alf_data

Finally, to execute the CMIS unit tests the bundled server must not be running since the these tests launch an embedded Web server that expects to use the same ports as the full server.