Creating the Component Dynamically Using Java

Key attributes and ways of usage @@ -106,28 +105,27 @@ = - + + - - - - - - - + + + + + + + - + value=3D"#{userBean.pollEnabled?'Stop':'Start'} P= olling" + reRender=3D"poll, grid"> + - - - - -... -]]> + + + + +...]]> = The example shows how date and time are updated on a page in com= pliance with data taken from a server. The Modified: trunk/docs/userguide/en/src/main/docbook/included/portlet.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/included/portlet.xml 2009-03-3= 0 23:18:08 UTC (rev 13312) +++ trunk/docs/userguide/en/src/main/docbook/included/portlet.xml 2009-03-3= 1 09:34:42 UTC (rev 13313) @@ -34,13 +34,11 @@

Creating the Component with a Page Tag To create the simplest variant on a page use the following synta= x: - - - ... - - -]]> + + + ... + +]]>

Modified: trunk/docs/userguide/en/src/main/docbook/included/push.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/included/push.xml 2009-03-30 2= 3:18:08 UTC (rev 13312) +++ trunk/docs/userguide/en/src/main/docbook/included/push.xml 2009-03-31 0= 9:34:42 UTC (rev 13313) @@ -80,8 +80,8 @@ System.out.println(evt.getSource()); //Some action } -... -]]> +} = +...]]> = Code for EventListener registration= in the bean is placed below: @@ -91,11 +91,12 @@ +...]]> = A page code for this example is placed below. = @@ -103,20 +104,19 @@ Example: + - - - - - - - - - - -... = -]]> + + + + + + + + + + +...]]> = The example shows how date is updated on a page = in compliance with data taken from a server. In the example Modified: trunk/docs/userguide/en/src/main/docbook/included/region.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/included/region.xml 2009-03-30= 23:18:08 UTC (rev 13312) +++ trunk/docs/userguide/en/src/main/docbook/included/region.xml 2009-03-31= 09:34:42 UTC (rev 13313) @@ -38,11 +38,11 @@

Creating on a page Here is an example of the region decoding on a page. - - - - - ]]> + + + + +]]>

Creating the Component Dynamically Using Java @@ -53,8 +53,7 @@ +...]]>

Key attributes and ways of usage @@ -72,10 +71,10 @@ Example: - - - - + + + + ]]> Hence, the <a4j:commandLink> @@ -83,12 +82,12 @@ The regions could be nested in any order, the server picks out a= nd decodes only the region, which contains a particular component that send= s a request. Example: - - - - - - + + + + + + ]]> Therefore, the external region is decoded for the

"li=
nk1"

and the internal one is decoded for the

"link2&=
quot;

. RichFaces allows setting Ajax responses rendering directly basin= g on component tree nodes without referring to the JSP (XHTML) page code. I= t could be defined by "selfRendered" attribute setting to "true" on @@ -99,8 +98,8 @@ Example: - - + + ]]> In this case, the processing is quicker and going on without ref= erring to a page code, but the HTML code that isn't saved in a compone= nt tree could be lost. Thus, this optimization should be very carefully per= formed and a usage of the additional components RichFaces (<a4j:outputPanel>) is requi= red. The processing could be also accelerated if a region decoded for= the processing passes straight away into Encode. But to update some data o= ut of the region or on another region, use the @@ -109,14 +108,12 @@ attribute set to "false" ("true" on default) to = change this behaviour. Example: - - - + + - - - + + ]]> This example shows that one of the regions is decoded when a lin= k is used inside. Nevertheless, = if after processing the "link1" is clicked, the= first region passes into Encode as a root = Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCSettings.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/modules/RFCSettings.xml 2009-0= 3-30 23:18:08 UTC (rev 13312) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCSettings.xml 2009-0= 3-31 09:34:42 UTC (rev 13313) @@ -87,11 +87,12 @@ Example: - - <context-param> - <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> - <param-value>com.sun.facelets.FaceletViewHandler</param-value&= gt; - </context-param> + + org.ajax4jsf.VIEW_HANDLERS + com.sun.facelets.FaceletViewHandler + +...]]> says that Facelets will of= ficially be the first, however AjaxViewHandler will be= a little ahead @@ -275,7 +276,7 @@ Example: +

Faces Servlet

javax.faces.webapp.FacesServlet

0 Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover= .xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2= 009-03-30 23:18:08 UTC (rev 13312) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2= 009-03-31 09:34:42 UTC (rev 13313) @@ -222,13 +222,12 @@ attribute is an id of the JSF component or an id list. A simple example is placed below: - ... - - ... - + ... -]]> + + ... + +...]]> The value of "reRender" attribute of the @@ -254,24 +253,23 @@ it more precisely. The following example shows the difference in appro= aches (both buttons will work successfully): - ... - - - ... - - - ... - + + ... + ... - - - ... - - ... - + + + ... + ... -]]> + + + ... + + ... + +...]]> It's also possible to use JSF EL expression as a value of t= he reRender attribute. It might be a property of types Set, Collection, Array or s= imple String. The EL for reRender is resolved right before the Render Response phase= . Hence, you @@ -304,11 +302,10 @@ on any Ajax request. For example, the following code allows to output = error messages regardless of what Ajax request causes the Validation phase failed. - - -... -]]> + + + +...]]> "limitToList" @@ -324,14 +321,13 @@ ajaxRendered=3D"true" is ignored. An example i= s placed below: - - - - - -... -]]> + + + + + + +...]]>

@@ -356,11 +352,10 @@ newest request will be sent to the server if you type very fast and ha= s typed the several characters already before the previous Ajax Response is back. = - - -... -]]> + + + +...]]> "requestDelay" @@ -501,8 +496,7 @@ view using the following: -... -]]> +...]]> Hence, to enable the queue for a single view page you need to d= efine the "disable" attribute with "false". @@ -523,8 +517,7 @@ the forms in order not to be recognized as a form-based queue. -... -]]> +...]]>

View scoped named queue @@ -550,12 +543,10 @@ = = - - + = - ...]]> In this example, two components(<a4j:queue>, <rich:comboBox>,) reference the named queue via the @@ -589,8 +580,8 @@ - - ... + + ... ...]]> = = @@ -601,7 +592,7 @@ - ... + ... ...]]> = However the implementation of the queue allows you to reference a= named queue from the form with a form-based queue. @@ -614,9 +605,9 @@ ... - - - + + + ...]]> = = @@ -742,14 +733,13 @@ <a4j:support> , it is a value of the parent component. An example is pla= ced below: - - - - - -... -]]> + + + + + + +...]]> In this example the request contains only the input component ca= uses the request generation, not all the components contained on a form, because of ajaxSingle=3D"true" usage. @@ -869,9 +859,8 @@ "true" or "false" , use the conditional statement = to return something only when you need to cancel the request. For example: +onsubmit=3D"if (mynosendfunct()=3D=3Dfalse){return false}" +...]]> "onclick" @@ -903,9 +892,8 @@ "data" variable. For example: -... -]]> + +...]]> RichFaces allows to serialize not only primitive types into JSON= format, but also complex types including arrays and collections. The beans should be se= rializable to be refered with @@ -936,7 +924,7 @@ taking the short ID of the component as a parameter. - + ...]]> @@ -953,21 +941,20 @@ provides possibility to update several child components separately wit= hout updating the whole page. - - - - - - - - -

- -

- -... -]]> + + + + + + + + + +

+ +

+ +...]]>

@@ -987,35 +974,33 @@ component between different Ajax components from different= regions. The following example shows it. - - - - - - - + + + + + + + + + + + + + - - - - - - - - - - -
- - - - - - -... -]]> + + + +
+ + + + + + + +...]]> In the example <a4j:support> and @@ -1306,13 +1291,12 @@ Example: - RichFaces Filter - richfaces - org.ajax4jsf.Filter - -... -]]> + + RichFaces Filter + richfaces + org.ajax4jsf.Filter + +...]]> Note: Fast Filter is deprecated and available only for backward compat= ibility with @@ -1352,50 +1336,43 @@ Example: - org.ajax4jsf.xmlparser.ORDER - NONE,NEKO,TIDY - - - - org.ajax4jsf.xmlparser.NONE - /pages/performance\.xhtml,/pages/default.*\.xhtml - - - - org.ajax4jsf.xmlparser.NEKO - /pages/repeat\.xhtml - - - - RichFaces Filter - richfaces - org.ajax4jsf.Filter - - - - richfaces - Faces Servlet - FORWARD - REQUEST - INCLUDE - -... -]]> + + org.ajax4jsf.xmlparser.ORDER + NONE,NEKO,TIDY + + + org.ajax4jsf.xmlparser.NONE + /pages/performance\.xhtml,/pages/default.*\.xhtml + + + org.ajax4jsf.xmlparser.NEKO + /pages/repeat\.xhtml + + + RichFaces Filter + richfaces + org.ajax4jsf.Filter + + + richfaces + Faces Servlet + FORWARD + REQUEST + INCLUDE + +...]]> The example shows that ORDER parameter defines the o= rder in which particular filter types are used for pages code correction. First of all "NONE" type is specified for the filter. T= hen two different sets of pages are defined for which two filter types (NONE and NEKO) ar= e used correspondingly. If a page relates to the first set that is defined in = the following way: - /pages/performance\.x= html,/pages/default.*\.xhtml, -]]> + /pages/performance\.x= html,/pages/default.*\.xhtml]]> it's not corrected, because filter type for this page is def= ined as "NONE". If a page is not from the first set, then "NEKO&= quot; type is set. If a page relates to the second set that is defined in the follow= ing way: - /pages/repeat\.xhtml<= /param-value>, -]]> + /pages/repeat\.xhtml<= /param-value>]]> then "NEKO" filter type is used for correction. If it&a= pos;s not related to the second set, "TIDY" type is set for the filter ("TIDY= " filter type is used for code correction). @@ -1412,21 +1389,19 @@ The following declaration in your web.xml allows loading the inte= grated script files. - org.richfaces.LoadScriptStrategy - ALL - -... -]]> + + org.richfaces.LoadScriptStrategy + ALL + +...]]> If you do not declare the

org.richfaces.LoadScriptStrategy<=
/code> in the
 			web.xml, it equals to:


 		
-        org.richfaces.LoadScriptStrategy
-        DEFAULT
-    
-...
-]]>
+
+	org.richfaces.LoadScriptStrategy
+    DEFAULT
+
+...]]>
 		 The third possible value is "NONE". You have no a speci=
al reason to use it
 			unless you obtain the newest (or modified) version of the script and wa=
nt to include it
 			manually in a page header. 
@@ -1447,12 +1422,11 @@
 		
 		 The following declaration allows to load only one integrated styl=
e sheet file. 
 		
-          org.richfaces.LoadStyleStrategy
-          ALL
-    
-...
-]]>
+
+	org.richfaces.LoadStyleStrategy
+    ALL
+
+...]]>
 		 The integrated style sheet contains style for all shipped compone=
nts. The
 			skinnability feature still works. 
 		 The "DEFAULT" value is a classical on-demand variant. <=
/para>
@@ -1641,8 +1615,7 @@
 			
 				Example:
 			
-			
-				<rich:panel> ... </rich:panel>
+			 ... ]]>
 			
 			 The code generates a panel component on a page, which consists o=
f two elements: a
 				wrapper 
@@ -1657,7 +1630,7 @@
 				Example:
 			
 			
-				<div class=3D"dr-pnl rich-panel"> ... </div>
+				 ... ]]>
 			
 			 dr-pnl is a CSS class specified in the framework via skin parame=
ters: 
 			
@@ -1686,8 +1659,7 @@
 				Example:
 			
 			
-				<rich:panel styleClass=3D"customClass"> ...
-				</rich:panel>
+				]]>
 			
 			 Could add some style properties from customClass to one particul=
ar panel, as a
 				result we get three styles: 
@@ -1695,8 +1667,9 @@
 				Example:
 			
 			
-				<div class=3D"dr_pnl rich-panel customClass"> ...
-				</div>
+ =

+	...
+]]>


 		
@@ -1929,12 +1902,11 @@
 						Example:
 					
 					
-        org.richfaces.SKIN
-        name
-    
-...
-]]>
+
+	org.richfaces.SKIN
+    name
+
+...]]>
 				
 				
 					 Put your <name>.skin.properties file in one=
 of the
@@ -1967,8 +1939,8 @@
 					 Create a custom render kit and register it in the faces-config=
.xml like
 						this: 
 					
-        NEW_SKIN
-        
+	NEW_SKIN
+    	
             org.ajax4jsf.framework.renderer.ChameleonRenderKitImpl
         
 ]]>
@@ -1977,11 +1949,9 @@
 					 Then you need to create and register custom renderers for the =
component
 						based on the look-and-feel predefined variables: 
 					
-        javax.faces.Command
-        javax.faces.Link
-        
-           newskin.HtmlCommandLinkRenderer
-        
+	javax.faces.Command
+    javax.faces.Link
+    newskin.HtmlCommandLinkRenderer
 ]]>
 				
 				
@@ -2019,8 +1989,8 @@
                 For example:
 			
 			
-  org.richfaces.SKIN
-  #{skinBean.skin}
+	org.richfaces.SKIN
+	#{skinBean.skin}
 ]]>
 			
 			
@@ -2042,13 +2012,13 @@
                 For example, "classic":
 			
 			
-  skinBean
-  SkinBean
-  session
-  
-   skin
-   classic
-  
+	skinBean
+	SkinBean
+	session
+	
+		skin
+		classic
+  	
 ]]>
 			
 			
@@ -2277,7 +2247,6 @@
    
 
 ...
-
 //gradient elements
 ...
 
@@ -2286,7 +2255,6 @@
     
     
 
-
 
     
         
@@ -3166,8 +3134,7 @@
 	org.richfaces.LoadStyleStrategy
 	NONE
 
-...
-]]>
+...]]>
 			 Additionally, you should include the style sheets that perform s=
kinning of the
 				RichFaces component and standard HTML controls. 
 			 In order to resolve the problem with extended skinning in Opera =
and Safari a
@@ -3175,11 +3142,9 @@
 				the browser type and enables extended skinning only for those browsers=
 that fully
 				support it. 
 			 The script can be activated by inserting this JavaScript code to=
 the page: 
-			
-window.RICH_FACES_EXTENDED_SKINNING_ON =3D true;
-
-]]>
+			
+	window.RICH_FACES_EXTENDED_SKINNING_ON =3D true;
+]]>
 			 When NO script loading strategy is used and extended skinning is=
 turned on then
 				corresponding warning message will appears in the console. 
 			 You also need to specify 
@@ -3190,11 +3155,9 @@
 				"rich-extended-skinning". 
 			 This is how you can include the style sheets to the page, in cas=
e automatic
 				skinnability implementation is disabled. 
-			
+			
 
-
-]]>
+]]>
 			
 				 Now it's necessary to use  a4j/versionXXX res=
ources prefix  instead of
 						a4j_versionXXX. Base64 encoder changed to use
@@ -3217,25 +3180,23 @@
 				 XML tags that form the mapping structure. Please study the=
 example
 				below. 
 			
-		
-		
-		
-		
-	
-...
-]]>
+
+	
+	
+	
+	
+
+...]]>
 			 During processing the code in the shown example is parsed into a=
 standard
 				CSS format. 
 			
+...]]>
 			 The 
 					"name"
 				 attribute of 
@@ -3254,10 +3215,9 @@
 				list. 
 			
-		
+	
 
-...
-]]>
+...]]>
 		
 		
 			
@@ -3282,8 +3242,7 @@
 -DartifactId=3DARTIFACT-ID
 -DgroupId=3DGROUP-ID
 -Dversion=3DVERSION
-...
-]]>
+...]]>
 			Primary keys for the command:
 			
 				
@@ -3451,10 +3410,9 @@
 					
 
+...]]>
 				
 				
 					 Using XCSS coding approach, the same way as XCSS files are nor=
mally
@@ -3470,8 +3428,7 @@
 	
 	
 
-...
-]]>
+...]]>
 				
 			
 			
@@ -3482,8 +3439,7 @@
 				folder of you skin project (the one that contains pom.xml file). 
 			
+...]]>
 			In addition Plug-n-Skin has a number of predefined gradients that=
 you can also use
 				to make your application look nicer. The given below code snippet show=
s how a
 				gradient can be used 
@@ -3501,8 +3457,7 @@
 		 
 	
 
-...
-]]>
+...]]>
 			 So, as you can see, the background-image CS=
S property is
 				defined with  <f:resource
 					f:key=3D"org.richfaces.renderkit.html.CustomizeableGradient"=
;>
@@ -3521,8 +3476,7 @@
     org.ajax4jsf.SKIN
     SKIN-NAME
 
-...
-]]>
+...]]>
 			
 				
 					
@@ -3549,9 +3503,7 @@
 					folders were created there. 
 				 Next, we will use Maven to add all needed files to the skin pro=
ject. This
 					will done by the following command: 
-				
+				=

 				 As you remember from the previous section "-DbaseSkin"=
; key defines
 					what RichFaces built-in skin to be used as a base one,
 					"-DcreateExt=3Dtrue" determines that the new skin will come=
 with XCSS
@@ -3595,9 +3547,8 @@
 					this. 
 				
+	font-weight: bold;
+}]]>
 				All the changes that were planned to be preformed are done and n=
ow you can
 					proceed to building the new PlugnSkinDemo skin and import it into the=
 project.
 					As you read in the previous section, the skin should be built in the
@@ -3616,23 +3567,19 @@
 					
 						Add the new skin's name to the "web.xml" file. =
It is
 							done like this
-						
-  org.ajax4jsf.SKIN
-  PlugnSkinDemo
- 
-]]>
+						
+	org.ajax4jsf.SKIN
+	PlugnSkinDemo
+]]>
 					
 				
 				 Please, do not forget that standard controls skinning has to be=
 enabled in
 					the "web.xml" file, which can be done by adding the followi=
ng code to
 					the "web.xml" file: 
-				
-  org.richfaces.CONTROL_SKINNING
-  enable
- 
-]]>
+				
+	org.richfaces.CONTROL_SKINNING
+	enable
+]]>
 				The result of both operations is displayed on the figure below.<=
/para>
 				
 					Plug-n-Skin feature in action. 


--===============4436090692081083069==--