[
https://issues.jboss.org/browse/AS7-5215?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-5215:
--------------------------------
Summary: Deployments unnecessarily trigger Framework create service (was:
Deployments unecessarily trigger Framework create service)
Git Pull Request:
https://github.com/jbossas/jboss-as/pull/2751 (was:
https://github.com/jbossas/jboss-as/pull/2751)
Deployments unnecessarily trigger Framework create service
----------------------------------------------------------
Key: AS7-5215
URL:
https://issues.jboss.org/browse/AS7-5215
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Non-OSGi deployments are registered with the resolver environment (XEnvironment) so that
bundle can define requirements on the package capabilities of those deployments.
There is plenty of processing needed in order to obtain those non-osgi capabilities and
to register them with the environment. The OSGi resolver may however never be activated
and there may never be any (bundle) deployment that defines requirements on those
capabilities.
This processing should be lazy and triggered by an actual resolve request.
Remove this from FrameworkActivateProcessor
{code}
// Always make the system context & the environment available
phaseContext.addDeploymentDependency(Services.SYSTEM_CONTEXT,
OSGiConstants.SYSTEM_CONTEXT_KEY);
phaseContext.addDeploymentDependency(Services.ENVIRONMENT,
OSGiConstants.ENVIRONMENT_KEY);
{code}
and do this more intelligently.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira