Investigate RequiredState for bundle deployments ------------------------------------------------ Key: JBOSGI-53 URL: https://jira.jboss.org/jira/browse/JBOSGI-53 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.x If you don't want the exception then you need to control the "required state" of the deployment such that it doesn't move to "Installed" and instead remains the unresolved state (Described?). There already is a method to change the "required state" of an existing deployment DeployerClient.change(deploymentName, DeploymentState); but there's nothing currently that lets you set it at initial deployment, e.g. something like DeployerClient.deploy(Deployment, DeploymentState); // DOES NOT EXIST -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira