Often one needs to provide similar, yet slightly different [[AlternativeBehavior]]s of the system. This page describes various levels on which such [[co-existence]] can take place.

Often one needs to provide similar, yet slightly different [[AlternativeBehavior]]s of the system. This page describes various levels on which such [[co-existence]] can take place.

TBD.

[[TBD]].

== Object level ==

== Object level ==

== Class level ==

== Class level ==

The behavior is associated with class - e.g. in [[Java]] one needs to load the class by two different classloaders to get different behavior. This way one can get multiple [[singleton]]s.

The behavior is associated with class - e.g. in [[Java]] one needs to load the class by two different [[ClassLoader]]s to get different behavior. This way one can get multiple [[singleton]]s.

The [[NetBeans Runtime Container]] falls into this category ([[NetBeans]] [[API]]s expose a lot of static getters). This was an intentional decision. We never wanted to have more than one [[GUI]] application in the process.

The [[NetBeans Runtime Container]] falls into this category ([[NetBeans]] [[API]]s expose a lot of static getters). This was an intentional decision. We never wanted to have more than one [[GUI]] application in the process.

== Cloud level ==

== Cloud level ==

To achieve [[AlternativeBehavior|parallel behavior]] of a complex system (kenai.com, netbeains.org) is often possible only with duplicating all its network.

To achieve [[AlternativeBehavior|parallel behavior]] of a complex system (kenai.com, netbeans.org) is often possible only with duplicating all its network.

The behavior is associated with class - e.g. in [[Java]] one needs to load the class by two different classloaders to get different behavior. This way one can get multiple [[singleton]]s.

The behavior is associated with class - e.g. in [[Java]] one needs to load the class by two different classloaders to get different behavior. This way one can get multiple [[singleton]]s.

== Call level ==

== Call level ==

== Object level ==

== Object level ==

One can configure two objects to have the same type (external interface), but slightly [[AlternativeBehavior|different behavior].

One can configure two objects to have the same type (external interface), but slightly [[AlternativeBehavior|different behavior]]. The [[OSGi]] falls into this category. It is possible to have two running [[OSGi]] containers in the same [[HotSpot|virtual machine]] quite easily (as the [[API]] doesn't have any static getters).

== Class level ==

== Class level ==

== Process level ==

== Process level ==

The behavior is the same throughout the process. System.getProperty("...") or various [[singleton]]s in core [[Java]] libraries ('''SecurityManager''') are example of such [[API]]s. One needs to start new [[Hotspot|virtual machine]] to get different behavior.

The behavior is the same throughout the process. System.getProperty("...") or various [[singleton]]s in core [[Java]] libraries ('''SecurityManager''') are example of such [[API]]s. One needs to start new [[HotSpot|virtual machine]] to get different behavior.

== Computer level ==

== Computer level ==

#REDIRECT [[AlternativeBehavior]]

Often one needs to provide similar, yet slightly different [[AlternativeBehavior]]s of the system. This page describes various levels on which such [[co-existence]] can take place.

 

 

 

 

 

 

 

 

 

 

 

 

 

#REDIRECT [[AlternativeBehaviour]]

#REDIRECT [[AlternativeBehavior]]