Examples of com.sun.appserv.addons.Configurator.configure()

• com.sun.appserv.addons.Configurator.configure()
  Performs the configuration of the addon. Typically it involves the creation of instance/domain specific artifacts and configuring the domain.xml, server.policy etc.

  When ConfigurationContext.ConfigurationType is DAS, the configurator is supposed to make any changes required for the domain. For example, it can insert a lifecycle-module element in the domain.xml with object-type="system-all", so that the lifecycle module will be available in all instances created in that domain.

  The configurator is expected to use the system property called com.sun.aas.AddonRoot for referring to the shared bits of the addon. For example, the location of the system-all lifecycle module may be specified as ${com.sun.aas.AddonRoot}//lib/lc-impl.jar

  When ConfigurationContext.ConfigurationType is INSTANCE, the configurator is expected to make any changes required for a particular instance. This may be creating a system-propery to specify a port number.

  If this method throw a AddonFatalException or RuntimeException, the appserver startup will not continue. If it throws AddonException, then the appserver startup will continue after displaying the error message. @param cc ConfigurationContext object.