Working with multiple configuration files

JSF 2.0 provides support for ordering the configuration resources. We can use partial ordering (represented by the <ordering> tag) and absolute ordering (represented by the <absolute-ordering> tag).

Note

Each document that is involved in the ordering plan is identified by the top-level tag, <name>.

Partial ordering is specific to a single configuration document. We can use the <before> and <after> tags to indicate that a certain document should be processed before or after another document. Nested inside the <before> and <after> tags, we may have the <others/> tag, which indicates that a certain document should be processed before (respectively after) all the other documents that are sorted.

Listed here is an example where we have documents A, B, C, and faces-config.xml alias D:

1. Document C needs to be executed before others; hence, it will be executed first:

   <name>C</name>
   <ordering>
     ...