Skip to main content

Source code revision

svn

summary: Issue 15493: In our earlier check-in, we had added an optimisation to avoid checking osgiContainer.isDeployed() for non-EE bundles. That has caused a regression updating hybrid applications. It happens when bundles get activated
revision: 44677
author: Sahoo
date: 2011-01-24 02:57:56 UTC (3 years)
message: Issue 15493: In our earlier check-in, we had added an optimisation to avoid checking osgiContainer.isDeployed()
for non-EE bundles. That has caused a regression updating hybrid applications. It happens when bundles get activated
in following order: hybrid application, osgi-javaee-base, osgi-web-container. In this case, the deploymentTask in JavaEEExtender
returns null, even though the hybrid bundles is actually deployed by DeployerAddedThread. As a result, any future updates
to the WAB is not picked up by the JavaEEExtender. The simple solution to this problem is to remove the
optimisation we had added, as a result, we now always check c.isDeployed() in bundleRemoved().
This code path only affects hybrid applications container.
See JIRA for 3.1 change control details.
Change Path Actions
M trunk/v3/osgi-javaee/osgi-javaee-base/src/main/java/org/glassfish/osgijavaeebase/JavaEEExtender.java
 
 
Close
loading
Please Confirm
Close