Practical RichFaces, Second Edition

Recommendations

Info

CHAPTER 2 GETTING STARTED INFO: BEFORE PROCESS_VALIDATIONS 3 Feb 8, 2011 2:39:49 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER PROCESS_VALIDATIONS 3 Feb 8, 2011 2:39:49 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE RENDER_RESPONSE 6 Feb 8, 2011 2:39:49 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER RENDER_RESPONSE 6 We arrived at Phase 3, validation failed and we jumped to Phase 6. So far it all makes sense. Now enter a valid value either for name or age. You should now see the console shown in Listing 2-41. Listing 2-41. After entering a valid value, you will see the following console INFO: BEFORE RESTORE_VIEW 1 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER RESTORE_VIEW 1 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE APPLY_REQUEST_VALUES 2 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER APPLY_REQUEST_VALUES 2 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE PROCESS_VALIDATIONS 3 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER PROCESS_VALIDATIONS 3 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE UPDATE_MODEL_VALUES 4 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER UPDATE_MODEL_VALUES 4 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE INVOKE_APPLICATION 5 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER INVOKE_APPLICATION 5 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE RENDER_RESPONSE 6 Feb 8, 2011 2:41:23 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER RENDER_RESPONSE 6 As validation didn’t fail, we competed all the phases. The next question is: do we need to go through all the phases when we are only validating? Probably not. When only validating, it’s enough to reach Phase 3 (Process Validations), and even if the input is correct we can jump to the Render Response phase. Why invoke the Update Model and Invoke Application phases when we actually don’t need to? Let’s make our request quicker. When the Register button is clicked, we don’t want to go through all the phases, we want to skip Update Model and Invoke Application phases. How do we achieve that? That’s where the bypassUpdates attribute is going to help us and described in Table 2-9. Table 2-9. bypassUpdates attribute Attribute Description bypassUpdates Skips Update Model and Invoke Application phases, useful for form validation. Listing 2-42 shows updating the JSF page and setting bypassUpdates="true".
Listing 2-42. Updating the JSF page CHAPTER 2 GETTING STARTED Running the page again and entering invalid values causes validation to fail; and from the Process Validations phase we jump to Render Response, as before. But, when we enter a valid value, we get the same behavior because we set bypassUpdates="true". For example, entering ‘Joe’ in the name field and then clicking outside the field should allow you to see it in the console shown in Listing 2-43. Listing 2-43. Example of the console after entering the name field INFO: AFTER RESTORE_VIEW 1 Feb 8, 2011 3:01:28 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE APPLY_REQUEST_VALUES 2 Feb 8, 2011 3:01:28 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER APPLY_REQUEST_VALUES 2 Feb 8, 2011 3:01:28 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE PROCESS_VALIDATIONS 3 Feb 8, 2011 3:01:28 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER PROCESS_VALIDATIONS 3 Feb 8, 2011 3:01:28 PM org.apache.catalina.core.ApplicationContext log INFO: BEFORE RENDER_RESPONSE 6 Feb 8, 2011 3:01:28 PM org.apache.catalina.core.ApplicationContext log INFO: AFTER RENDER_RESPONSE 6 Once we reach the Process Validation phase, the component is validated and we go directly to the Render Response phase. Again, there is no need to continue with the other phases because they will be invoked when the Register button is clicked. So to summarize, bypassUpdates is useful when doing Ajaxbased validation. JavaScript Interactions or Callback Events Firing an Ajax request doesn’t require writing any JavaScript code. Using or the more advanced makes it possible to fire an Ajax request from any component. However, there might be a situation where you might want to call or inject a custom JavaScript function before or after the Ajax
Page 2 and 3: 488 CHAPTER 9: Super Jumper: A 2D O
Page 4 and 5: Introduction We have been involved
Page 6 and 7: CHAPTER 1 THE BASICS Figure 1-1. R
Page 8 and 9: CHAPTER 1 THE BASICS JSF Is Very E
Page 10 and 11: CHAPTER 1 THE BASICS As you can se
Page 12 and 13: CHAPTER 1 THE BASICS This exam
Page 14 and 15: CHAPTER 1 THE BASICS Validation. I
Page 16 and 17: CHAPTER 1 THE BASICS When Starting
Page 18 and 19: CHAPTER 2 GETTING STARTED org.ri
Page 20 and 21: CHAPTER 2 GETTING STARTED Listing
Page 22 and 23: CHAPTER 2 GETTING STARTED • deep
Page 26 and 27: CHAPTER 2 GETTING STARTED In JSF,
Page 28 and 29: CHAPTER 2 GETTING STARTED When the
Page 34 and 35: CHAPTER 2 GETTING STARTED Let’s
Page 36 and 37: CHAPTER 2 GETTING STARTED } } publ
Page 42 and 43: CHAPTER 2 GETTING STARTED request
Page 44 and 45: CHAPTER 2 GETTING STARTED Figure 2
Page 46 and 47: CHAPTER 2 GETTING STARTED onbegin=
Page 48 and 49: CHAPTER 3 A4J:* TAGS, FEATURES, AN
Page 90 and 91:
CHAPTER 4 GETTING STARTED WITH RIC
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
CHAPTER 5 RICH INPUT AND SELECT CO
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
CHAPTER 6 RICH PANEL AND OUTPUT CO
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
CHAPTER 7 RICH DATA ITERATION COMP
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
C H A P T E R 8 Rich Menu Compon
Page 250 and 251:
Listing 8-2. The bean code @Managed
Page 252 and 253:
CHAPTER 8 RICH MENU COMPONENTS You
Page 254 and 255:
CHAPTER 8 RICH MENU COMPONENTS Whe
Page 256 and 257:
Listing 8-10. JSF page CHAPTER 8 R
Page 258 and 259:
Listing 8-12. Adding icons to the m
Page 260 and 261:
Table 8-1. JavaScript API Method N
Page 262 and 263:
CHAPTER 8 RICH MENU COMPONENTS The
Page 264 and 265:
CHAPTER 8 RICH MENU COMPONENTS act
Page 266 and 267:
Listing 8-20. Defining a group ...
Page 268 and 269:
C H A P T E R 9 Rich Tree Compon
Page 270 and 271:
} } @Override public boolean getAll
Page 272 and 273:
CHAPTER 9 RICH TREE COMPONENTS Cre
Page 274 and 275:
Figure 9-3. built using the RichFa
Page 276 and 277:
} public void setData(String data)
Page 278 and 279:
CHAPTER 9 RICH TREE COMPONENTS mar
Page 280 and 281:
CHAPTER 9 RICH TREE COMPONENTS Now
Page 282 and 283:
} rootNode = new TreeNodeImpl(); Ri
Page 284 and 285:
Using CHAPTER 9 RICH TREE COMPONE
Page 286 and 287:
CHAPTER 9 RICH TREE COMPONENTS Tha
Page 288 and 289:
} private List rootFiles; private F
Page 290 and 291:
C H A P T E R 10 Rich Drag-and-D
Page 292 and 293:
Listing 10-3 shows the code with al
Page 294 and 295:
CHAPTER 10 RICH DRAG-AND-DROP COMP
Page 296 and 297:
Page 298 and 299:
Listing 10-11 shows the modified pa
Page 300 and 301:
Listing 10-12. Adding the CSS class
Page 302 and 303:
Page 304 and 305:
Figure 10-12. Tree component CHAPTE
Page 306 and 307:
Page 308 and 309:
CHAPTER 11 RICH VALIDATION Note R
Page 310 and 311:
CHAPTER 11 RICH VALIDATION
Page 312 and 313:
CHAPTER 11 RICH VALIDATION Of cour
Page 314 and 315:
CHAPTER 11 RICH VALIDATION Figure
Page 316 and 317:
CHAPTER 11 RICH VALIDATION } @NotN
Page 318 and 319:
CHAPTER 11 RICH VALIDATION to serv
Page 320 and 321:
CHAPTER 12 RICH COMPONENTS JAVASCR
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
C H A P T E R 13 Skins RichFaces
Page 336 and 337:
Figure 13-2. Rich panel and tabs in
Page 338 and 339:
tabFamilyFont=Arial, Verdana, sans-
Page 340 and 341:
Figure 13-3. Rich panel and tabs in
Page 342 and 343:
Table 13-5. Skin Parameters for the
Page 344 and 345:
Figure 13-4. Rich panel in ruby ski
Page 346 and 347:
Keep in mind that redefining CSS pr
Page 348 and 349:
Listing 13-19. The managed bean @Ma
Page 350 and 351:
Listing 13-23. Equivalent code samp
Page 352 and 353:
Using #{richSkin} Implicit Object C
Page 354 and 355:
Figure 13-14. Highlighting currentl
Page 356 and 357:
CHAPTER 14 RICHFACES CDK: BUILDING
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Index A a4j advanced execute op
Page 386 and 387:
common attributes, 377 component co
Page 388 and 389:
Hibernate Core (version 3.6.2), 228
Page 390 and 391:
JSF page, 112 pop-up selection, 111
Page 392 and 393:
Max Katz Ilya Shaikovsky Practical
Page 394 and 395:
To Victoria and Evelyn —Max I ded
Page 396 and 397:
CONTENTS Understanding That JSF App
Page 398 and 399:
CONTENTS Using ...................
Page 400 and 401:
CONTENTS Table Sorting by Multiple
Page 402 and 403:
CONTENTS Chapter 13: Skins ........
Page 404 and 405:
About the Technical Reviewer Jason
show all

Practical RichFaces, Second Edition

Create successful ePaper yourself

Delete template?

Save as template?