You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Angelo van der Sijpt (Updated) (JIRA)" <ji...@apache.org> on 2011/12/14 14:43:30 UTC
[jira] [Updated] (FELIX-3272) Add property to allow foreign
resource processors
[ https://issues.apache.org/jira/browse/FELIX-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Angelo van der Sijpt updated FELIX-3272:
----------------------------------------
Attachment: FELIX-3272.patch
Patch implementing the proposed solution.
> Add property to allow foreign resource processors
> -------------------------------------------------
>
> Key: FELIX-3272
> URL: https://issues.apache.org/jira/browse/FELIX-3272
> Project: Felix
> Issue Type: Improvement
> Components: Deployment Admin
> Affects Versions: deploymentadmin-0.9.0
> Reporter: Angelo van der Sijpt
> Attachments: FELIX-3272.patch
>
>
> DeploymentAdmin is built in such a way, that a deployment package is self-contained. However, in my case, I want to use a ResourceProcessor that is already on the system to process a configuration resource; if I do this, this will give me a DeploymentException.CODE_FOREIGN_CUSTOMIZER.
> Just like system property org.apache.felix.deploymentadmin.stopunaffectedbundle can customize the behavior of deployment admin, I propose a new property: org.apache.felix.deploymentadmin.allowforeigncustomizers , which allows ResourceProcessors that are already on the system to process resources in a deployment package. This should not be default behavior, so a system property should be in order.
> I will attach a patch for this shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira