As we near the top of the Cocoon processing tree, we find machinery that comes as part of the implementation of the user application. These are the files that provide the configuration and login specific to the application.
A Cocoon application has several configuration files. These have many purposes, including the following:
Define what components are used by the application
Configure the components
Set up data sources and connection pools
Tune Cocoon and the application
Configure what debugging data is collected
The two most important configuration files are cocoon.xconf and web.xml, both of which can be found under the WEB-INF folder of the Web application.
If a developer has extended Cocoon and added his or her own components, these form part of the implementation layer. For example, components that handle the generation, transformation, and process flow of a response are all likely to be components that have forms bespoke to the application. These will provide processing capability that is specific to the application, reflecting business rules and requirements that are not indigenous to Cocoon itself.
Even if the developer has not extended the Java-based components themselves, it is highly likely that the application will utilize XSP, the XML-based server-side scripting language that is part of Cocoon. This logic effectively is part of the custom components because XSP files are compiled into generator components for execution.
If the developer develops libraries of code as logicsheets, these too are included in the implementation layer.