chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Carter (JIRA)" <>
Subject [jira] [Created] (CMIS-682) Using Chemistry OpenCMIS in ServiceMix 4.5
Date Fri, 28 Jun 2013 21:51:22 GMT
Jason Carter created CMIS-682:

             Summary: Using Chemistry OpenCMIS in ServiceMix 4.5
                 Key: CMIS-682
             Project: Chemistry
          Issue Type: Bug
    Affects Versions: OpenCMIS 0.9.0
         Environment: Linux, ServiceMix 4.5
            Reporter: Jason Carter
            Priority: Critical

Sorry if my acronyms are incorrect, newbie...

We are using chemistry-opencmis-client-impl in a Module used by a Camel Route Bean.  It is
built using Maven.  And we are seeing an error when we try and call getRepositories when running
under ServiceMix 4.5:

Caused by: Provider
not found
	at org.apache.chemistry.opencmis.commons.impl.XMLUtils.<clinit>(
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AtomPubParser.parse(
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.parse(
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.getRepositoriesInternal(
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.RepositoryServiceImpl.getRepositoryInfos(
	at org.apache.chemistry.opencmis.client.bindings.impl.RepositoryServiceImpl.getRepositoryInfos(
	at org.apache.chemistry.opencmis.client.runtime.SessionFactoryImpl.getRepositories(
	at org.apache.chemistry.opencmis.client.runtime.SessionFactoryImpl.getRepositories(
	at com.avid.gam.assetsystem.CmisSessionHolder.initSession(
	at com.avid.gam.assetsystem.AlfrescoAssetSystem.createSession(
	at com.avid.gam.assetsystem.AssetSystemFactory.getByKey(
	at com.avid.gam.assetsystem.AssetSystemFactory.getAssetSystem(
	at com.avid.gam.route.GamRouteBean.saveOrder(

As far as I can tell we are including all required dependencies in the POM.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message