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

[gp...@apache.org]

Author: gpetracek
Date: Sun May 26 16:18:12 2013
New Revision: 1486427

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

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

Modified: incubator/deltaspike/site/trunk/content/deltaspike/jsf.mdtext
URL: http://svn.apache.org/viewvc/incubator/deltaspike/site/trunk/content/deltaspike/jsf.mdtext?rev=1486427&r1=1486426&r2=1486427&view=diff
==============================================================================
--- incubator/deltaspike/site/trunk/content/deltaspike/jsf.mdtext (original)
+++ incubator/deltaspike/site/trunk/content/deltaspike/jsf.mdtext Sun May 26 16:18:12 2013
@@ -677,7 +677,7 @@ By just using `@MySecured` in view-confi
 
 It's also possible do register different callback-types per view-meta-data. An example can be found at `ViewControllerRef` which registers different callback-types for `InitView`, `PreViewAction`, `PreRenderView` and `PostRenderView`. In this case it's needed to use the type of the callback (= class of the annotation) as additional parameter for `#getExecutableCallbackDescriptor`.
 
-Creating Custom inline Meta-Data via @InlineViewMetaData
+### Creating Custom inline Meta-Data via @InlineViewMetaData
 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).