Each dynamic component must be coded as a Java class that implements one of the interfaces listed in Arbortext PE Request Manager Components. Each object must provide an init method that takes as parameters the Arbortext Publishing Engine Request Context object being constructed and the com.arbortext.e3cf object that describes the object being initialized. Because the init method is called while the Arbortext Publishing Engine Request Context is being constructed, not all of the Arbortext Publishing Engine Request Context functionality is available. In particular, the Arbortext PE sub-process pools are initialized after many of the Dynamic Components have been initialized, so no dynamic component except an initializer can obtain an Arbortext PE sub-process during its initialization. For example, a cache manager that wants to use an Arbortext PE sub-process to obtain information can't do so; instead, you must write an initializer that can run after the Arbortext PE sub-process pools have been initialized.