Category: Container
Status: Closed

Severity: MEDIUM
Reported against release: 0.8
Fixed in release: 0.9

PROBLEM:

The PropertyInitializer is being loaded by the container core.  This 
prevents applications from having their own properties read in by the 
initializer.  This should be removed from the container core.

ANALYSIS:

The Container implementation is divided into two pieces, a core and a 
part that provides the net.openwings.container.Container service. The 
service portion is isolated in its own ClassLoader so that it does not 
conflict with processes in the container. Changes are required to the 
core and service portions so that all activity related to property 
initialization is performed in the service portion. That way, processes 
started in the container can use the property initializer and get their 
own properties.

Container Core changes: The Container core needs to be modified so that 
it does not call the net.openwings.identity.PropertyInitializer.

Container Service changes: The container profile (currently stored in 
the ContainerManagerPolicy.xml file, used by the Container Manager to 
start containers) needs to be modified so that the $OW_HOME/openwings-
0.8/policies directory is moved from the classpath of the container 
core to the service portion classpath, specified by the 
com.mot.openwings.container.classpath property (in future versions, 
this property will become com.gd.openwings.container.classpath).

back to top

home | vision | search | in the news | faq | registration | open forum | tutorial | bug database
 API | download | expert teams | process management office | projects | links | terms of use

© Copyright 2001-2006 General Dynamics C4 Systems. All rights reserved.