The message you see tells us 'yes, we recognized your artifact, but we don't
have a resource processor bundle available.' During deployment, this bundle
will be put into the deployment package, and shipped along with the artifact so
we can handle it (see section 114.10 of the OSGi Compendium spec).
You need to add a resource processor bundle to the system, just as you would
import any other bundle you want to provision (note that it will not be shown
in the list of artifacts, since it doesn't make sense to provision it
yourself). There is an AutoConf processor available as part of Felix'
Deployment Admin.
Angelo
On Aug 18, 2011, at 10:41 AM, Bram de Kruijff wrote:
> Hi List,
>
> trying to get metatype configuration deployed through ACE, but am stuck.
>
> First, I've create a artifact through the REST API and that seems all in order
>
> "attributes": {
> "artifactName": "Amdatu Web - HTTP Config",
> "artifactDescription": "Amdatu Web - HTTP Config",
> "mimetype": "application/xml:osgi-autoconf",
> "url":
> "file:///C:/bramk/Amdatu/svn/amdatu-trunk/amdatu-release-ams/org.apache.felix.http.xml",
> "filename": "org.apache.felix.http.xml"
> }
>
> Now when I try to associate this artifact with a feature I get
>
> "Unable to create deployment version: there is no resource processing
> bundle available that publishes org.osgi.deployment.rp.autoconf
> java.lang.IllegalStateException: Unable to create deployment version:
> there is no resource processing bundle available that publishes
> org.osgi.deployment.rp.autoconf"
>
>
> So it seems the ConfigurationHelper recognized the mimetype and sets
> the processor to org.osgi.deployment.rp.autoconf. However there seems
> to be no processor? It is not in my runtime and grepping the ACE
> codebase there is only resourceprocessor.useradmin.
>
> Should I create my own processor or am I missing something here?
>
> Thanks,
> Bram
