From fd0033951e533a6a9b7bd870e1f118354b5f84d1 Mon Sep 17 00:00:00 2001 From: xue <> Date: Tue, 13 Feb 2007 14:16:09 +0000 Subject: updated tutorial pages about external config inclusion. --- .../protected/pages/Configurations/AppConfig.page | 29 ++++++++++++++++------ .../protected/pages/Configurations/PageConfig.page | 9 ++++--- 2 files changed, 26 insertions(+), 12 deletions(-) (limited to 'demos/quickstart/protected/pages/Configurations') diff --git a/demos/quickstart/protected/pages/Configurations/AppConfig.page b/demos/quickstart/protected/pages/Configurations/AppConfig.page index b0a3c7c3..45e71a1d 100644 --- a/demos/quickstart/protected/pages/Configurations/AppConfig.page +++ b/demos/quickstart/protected/pages/Configurations/AppConfig.page @@ -5,7 +5,8 @@ Application configurations are used to specify the global behavior of an application. They include specification of path aliases, namespace usages, module and service configurations, and parameters.

-Configuration for an application is stored in an XML file named application.xml, which should be located under the application base path. Its format is shown in the following, +Configuration for an application is stored in an XML file named application.xml, which should be located under the application base path. Its format is shown in the following. Complete specification of application configurations can be found in the DTD and XSD files. +

@@ -15,32 +16,44 @@ Configuration for an application is stored in an XML file named application. - - - + + + + -

+ +

-Complete specification of application configurations can be found in the DTD and XSD files. +An external configuration file has the same format as described above. Although the name of the root element does not matter, it is recommended to be <configuration>. External configurations will append to the main configuration. For example, if a path alias is specified in an external configuration, it will become available in addition to those aliases specified in the main configuration.

+

-By default without explicit configuration, a PRADO application when running will load a few core modules, such as THttpRequest, THttpResponse, etc. It will also provide the TPageService as a default service. Configuration and usage of these modules and services are covered in individual sections of this tutorial. Note, if your application takes default settings for these modules and service, you do not need to provide an application configuration. However, if these modules or services are not sufficient, or you want to change their behavior by configuring their property values, you will need an application configuration. +By default without explicit configuration, a PRADO application will load a few core modules, such as THttpRequest, THttpResponse, etc. It will also provide the TPageService as a default service. Configuration and usage of these modules and services are covered in individual sections of this tutorial. Note, if your application takes default settings for these modules and service, you do not need to provide an application configuration. However, if these modules or services are not sufficient, or you want to change their behavior by configuring their property values, you will need an application configuration.

$Id$
\ No newline at end of file diff --git a/demos/quickstart/protected/pages/Configurations/PageConfig.page b/demos/quickstart/protected/pages/Configurations/PageConfig.page index dc0c2543..e41019af 100644 --- a/demos/quickstart/protected/pages/Configurations/PageConfig.page +++ b/demos/quickstart/protected/pages/Configurations/PageConfig.page @@ -19,6 +19,10 @@ The format of a page configuration file is as follows, + + + + @@ -26,13 +30,10 @@ The format of a page configuration file is as follows, - - -

-The <paths>, <modules> and <parameters> are similar to those in an application configuration. The <authorization> specifies the authorization rules that apply to the current page directory and all its subdirectories. It will be explained in more detail in future sections. The <pages> element specifies the initial values for the properties of pages. Each <page> element specifies the initial property values for a particular page identified by the id attribute. Initial property values given in the <pages> element apply to all pages in the current directory and all its subdirectories. +The <paths>, <modules>, <parameters> and <include> are similar to those in an application configuration. The <authorization> element specifies the authorization rules that apply to the current page directory and all its subdirectories. For more details, see authentication and authorization section. The <pages> element specifies the initial values for the properties of pages. Each <page> element specifies the initial property values for a particular page identified by the id attribute. Initial property values given in the <pages> element apply to all pages in the current directory and all its subdirectories.

Complete specification of page configurations can be found in the DTD and XSD files. -- cgit v1.2.3