It's part of the deployment admin project in Felix, so you can get it from
there. Next step is to upload it to the repository just like you would for a
bundle. Once it's in the OBR and registered in ACE, you can use it. You won't
see it in the UI, but whenever you deploy a configuration, it will
automatically get shipped with the deployment package.
Greetings, Marcel
On 18 Aug 2011, at 10:41 , 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
