svn commit: r1553510 - /deltaspike/site/trunk/content/jsf.mdtext

[gp...@apache.org]

Author: gpetracek
Date: Thu Dec 26 16:53:00 2013
New Revision: 1553510

URL: http://svn.apache.org/r1553510
Log:
updated content

Modified:
    deltaspike/site/trunk/content/jsf.mdtext

Modified: deltaspike/site/trunk/content/jsf.mdtext
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/jsf.mdtext?rev=1553510&r1=1553509&r2=1553510&view=diff
==============================================================================
--- deltaspike/site/trunk/content/jsf.mdtext (original)
+++ deltaspike/site/trunk/content/jsf.mdtext Thu Dec 26 16:53:00 2013
@@ -682,7 +682,7 @@ It's also possible do register different
 This annotation can be used for view-meta-data which can be placed on other classes than view-config-classes. It's used e.g. for `@ViewRef`.
 Via a `TargetViewConfigProvider` it's possible to point to the view-config the meta-data should get applied to and via `InlineMetaDataTransformer` it's possible to convert it to a different meta-data-representation (which allows that at runtime you only have to support one side since the inline-meta-data was converted to the same meta-data representation which is used for the normal view-meta-data).
 
-### Path-Validation
+## Path-Validation
 
 DeltaSpike (after v0.5) validates your configs out-of-the-box. The application will fail to start, if there is an invalid config (e.g. a view-config without a corresponding view).
 Right now the validation is restricted to folders and view-ids with .xhtml or .jsp as suffix. Other view-ids (e.g. *.faces) don't get checked. In such cases a custom validator can be used (e.g. based on `ViewConfigPathValidator`).