The following metadata XML files are generated once the Fusion web application generation wizard is finished:
1. adf-settings.xml: The adf-settings.xml file keeps the UI project configurations.
2. faces-config.xml: The faces-config.xml file contains the configurations for a web application built using JSF. This file allows to configure managed beans, data convertors, and validators used in the UI, navigation cases, global resource bundles, view handlers, page lifecycle phase listeners, and custom lifecycle factory implementation for the application.
3. adfc-config.xml: ADF Faces is built on the top of the JSF with a lot of extra features, which are not covered by the core JSF. ADF Faces uses adfc-config.xml to keep its configurations. We use adfc-config.xml to keep the navigation cases and managed bean definitions. To run a fusion web application we need both faces-config.xml and adfc-config.xml files- which is true even if we dont have any custom congif entries in faces-config.xml.
4. trinidad-config.xml: The generated trinidad-config.xml files contain only the skin family name. trinidad-config.xml can be used to override the default configurations for accessibility settings, locale settings, state management and so on.
5. web.xml: The web.xml file acts as a deployment descriptor for a java-based web application. A default web.xml file will be created with default settings. The default entries include context parameters for configuring the runtime state of the system, security files, data binding filters for web pages, and resource look up filters. It also includes servlet context listeners for initializing the management and monitoring services for view and model layers.
6. adf-config.xml: The adf-config.xml file contains application-level settings, which manage the run time infrastructure-such as failover behavior for the application modules, global fetch limit for all the view objects, caching of resource bundles, automated refresh of page page bindings and so on.
7. weblogic-application.xml: This file is the Weblogic server-specific deployment descriptor.
Data Base related XML files:
1. Connections.xml : This file contains the database connection detail that we create for development. If the application consumes web services, the corresponding connection uniform resource locator (URL) will also be present in this file.
2. jps-config.xml: The jps-config.xml file is used to store the Oracle platform security configurations. The location of this file is configured in the adf-config.xml.
1. adf-settings.xml: The adf-settings.xml file keeps the UI project configurations.
2. faces-config.xml: The faces-config.xml file contains the configurations for a web application built using JSF. This file allows to configure managed beans, data convertors, and validators used in the UI, navigation cases, global resource bundles, view handlers, page lifecycle phase listeners, and custom lifecycle factory implementation for the application.
3. adfc-config.xml: ADF Faces is built on the top of the JSF with a lot of extra features, which are not covered by the core JSF. ADF Faces uses adfc-config.xml to keep its configurations. We use adfc-config.xml to keep the navigation cases and managed bean definitions. To run a fusion web application we need both faces-config.xml and adfc-config.xml files- which is true even if we dont have any custom congif entries in faces-config.xml.
4. trinidad-config.xml: The generated trinidad-config.xml files contain only the skin family name. trinidad-config.xml can be used to override the default configurations for accessibility settings, locale settings, state management and so on.
5. web.xml: The web.xml file acts as a deployment descriptor for a java-based web application. A default web.xml file will be created with default settings. The default entries include context parameters for configuring the runtime state of the system, security files, data binding filters for web pages, and resource look up filters. It also includes servlet context listeners for initializing the management and monitoring services for view and model layers.
6. adf-config.xml: The adf-config.xml file contains application-level settings, which manage the run time infrastructure-such as failover behavior for the application modules, global fetch limit for all the view objects, caching of resource bundles, automated refresh of page page bindings and so on.
7. weblogic-application.xml: This file is the Weblogic server-specific deployment descriptor.
Data Base related XML files:
1. Connections.xml : This file contains the database connection detail that we create for development. If the application consumes web services, the corresponding connection uniform resource locator (URL) will also be present in this file.
2. jps-config.xml: The jps-config.xml file is used to store the Oracle platform security configurations. The location of this file is configured in the adf-config.xml.
No comments:
Post a Comment