Beginning Java EE 6 with GlassFish 3, Second Edition

More documents

Recommendations

Info

CHAPTER 12 ■ PROCESSING AND NAVIGATIONif (!matcher.find()) {String message = MessageFormat.format("{0} is not a valid isbn format", componentValue);FacesMessage facesMessage = new FacesMessage(SEVERITY_ERROR, message, message);throw new ValidatorException(facesMessage);}}}The code in Listing 12-13 starts by associating the validator with the name isbnValidator, to allow itto be used in a page. It implements the Validator interface and adds the validation logic to thevalidate() method. It checks, with a regular expression, that the ISBN has the right format. If not, it addsa message to the context and throws an exception. JSF will automatically resume the life cycle of thepage, recall the page, and display the error message. You can employ this custom validator in your pagesusing the validator attribute or embedding a tag:// orAjaxThe HTTP protocol is based on a request/response mechanism: a client needs something, sends arequest, and receives a response from the server, usually an entire web page. The communicationfollows this direction: a client requests something from the server, and not the other way around.However, web applications must provide rich and responsive interfaces and must react to server events,update parts of the page, aggregate widgets, and so on. In a normal request/response situation, theserver would have to send the entire web page back even if only a small portion had to change. If thepage has a significant size, you’ll overload the bandwidth and have poor responsiveness as the browserwould need to load the entire page. If you want to increase the browser’s responsiveness and improvethe user’s browsing experience, you need to update only small portions of the page. And this can bedone with Ajax.Ajax (stands for Asynchronous JavaScript and XML) is a set of web development techniques used tocreate interactive web applications. Ajax allows web applications to retrieve portions of data from theserver asynchronously without interfering with the display and behavior of the existing page. Once thedata is received by the client, only the portions requiring updating using the Document Object Model(DOM) of the page and JavaScript are needed. There is also a mechanism called Reverse Ajax (or Cometprogramming) for pushing data from the server back to the browser. These mechanisms are used inmost of our daily web applications, and JSF 2.0 has introduced support for them.General ConceptsThe term Ajax was coined in 2005 as a set of alternative techniques for loading asynchronous data intoweb pages. Back in 1999, Microsoft created the XMLHttpRequest object as an ActiveX control in InternetExplorer 5. In 2006, the World Wide Web Consortium (W3C) released the first specification draft for the368
CHAPTER 12 ■ PROCESSING AND NAVIGATIONXMLHttpRequest object, which is now supported by most browsers. At the same time, several companiesbrainstormed about how to ensure that Ajax could be the industry standard for a rich applicationplatform based on open technologies. The result of this work was the creation of the OpenAjax Alliance,which consists of vendors, open source projects, and companies using Ajax-based technologies.As shown in Figure 12-7, in traditional web applications, the browser has to ask for the full HTMLdocuments from the server. The user clicks a button to send or get the information, waits for the serverto respond, and then receives the entire page that the browser loads. Ajax, on the other hand, usesasynchronous data transfer (HTTP requests) between the browser and the server, allowing web pages torequest small bits of information (JSON or XML data) from the server instead of whole pages. The userstays on the same page while a piece of JavaScript requests or sends data to a server asynchronously, andonly portions of the page are actually updated, making web application faster and more user friendly.Figure 12-7. Plain HTTP calls vs. Ajax HTTP callsIn principle, Ajax is based on the following:• XHTML and CSS for presentation.• DOM for dynamic display and interaction with data.• XML and XSLT for the interchange, manipulation, and display of XML data.• The XMLHttpRequest object for asynchronous communication.• JavaScript to bring these technologies together.369
Page 1:
The EXPERT’s VOIce ® in Java tm
Page 4 and 5:
Beginning Java EE 6 Platform with G
Page 6 and 7:
Contents at a Glance■Foreword ...
Page 8 and 9:
■ CONTENTSSummary ...............
Page 10 and 11:
■ CONTENTSBulk Update ...........
Page 12 and 13:
■ CONTENTSStateful . ............
Page 14 and 15:
■ CONTENTSScripting Elements ....
Page 16 and 17:
■ CONTENTSMDB Model .............
Page 18 and 19:
■ CONTENTSFrom the Web to Web Ser
Page 20 and 21:
About the Author■ Antonio Goncalv
Page 22 and 23:
AcknowledgmentsWriting a book about
Page 24 and 25:
■ PREFACECONTENTSChapter 1 briefl
Page 27 and 28:
C H A P T E R 1■ ■ ■Java EE 6
Page 29 and 30:
CHAPTER 1 ■ JAVA EE 6 AT A GLANCE
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67:
Page 70 and 71:
CHAPTER 2 ■ JAVA PERSISTENCEJPA S
Page 72 and 73:
CHAPTER 2 ■ JAVA PERSISTENCEEclip
Page 74 and 75:
CHAPTER 2 ■ JAVA PERSISTENCEusing
Page 76 and 77:
CHAPTER 2 ■ JAVA PERSISTENCEFigur
Page 78 and 79:
CHAPTER 2 ■ JAVA PERSISTENCENote
Page 80 and 81:
CHAPTER 2 ■ JAVA PERSISTENCE■ N
Page 82 and 83:
CHAPTER 2 ■ JAVA PERSISTENCERunni
Page 84 and 85:
CHAPTER 2 ■ JAVA PERSISTENCE@Befo
Page 86 and 87:
CHAPTER 2 ■ JAVA PERSISTENCERunni
Page 88 and 89:
CHAPTER 3 ■ OBJECT-RELATIONAL MAP
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
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:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 149 and 150:
C H A P T E R 4■ ■ ■Managing
Page 151 and 152:
CHAPTER 4 ■ MANAGING PERSISTENT O
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
C H A P T E R 5■ ■ ■Callbacks
Page 195 and 196:
CHAPTER 5 ■ CALLBACKS AND LISTENE
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203:
Page 206 and 207:
CHAPTER 6 ■ ENTERPRISE JAVA BEANS
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 227 and 228:
C H A P T E R 7■ ■ ■Session B
Page 229 and 230:
CHAPTER 7 ■ SESSION BEANS AND THE
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
C H A P T E R 8■ ■ ■Callbacks
Page 265 and 266:
CHAPTER 8 ■ CALLBACKS AND INTERCE
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
C H A P T E R 9■ ■ ■Transacti
Page 281 and 282:
CHAPTER 9 ■ TRANSACTIONS AND SECU
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301:
Page 304 and 305:
CHAPTER 10 ■ JAVASERVER FACESUnde
Page 306 and 307:
CHAPTER 10 ■ JAVASERVER FACESList
Page 308 and 309:
CHAPTER 10 ■ JAVASERVER FACESList
Page 310 and 311:
CHAPTER 10 ■ JAVASERVER FACESJSR
Page 312 and 313:
CHAPTER 10 ■ JAVASERVER FACESWrit
Page 314 and 315:
CHAPTER 10 ■ JAVASERVER FACESpubl
Page 316 and 317:
CHAPTER 10 ■ JAVASERVER FACES•
Page 318 and 319:
CHAPTER 10 ■ JAVASERVER FACESAPre
Page 320 and 321:
CHAPTER 10 ■ JAVASERVER FACESorg.
Page 323 and 324:
C H A P T E R 11■ ■ ■Pages an
Page 325 and 326:
CHAPTER 11 ■ PAGES AND COMPONENTS
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344: CHAPTER 11 ■ PAGES AND COMPONENTS
Page 369: CHAPTER 11 ■ PAGES AND COMPONENTS
Page 372 and 373: CHAPTER 12 ■ PROCESSING AND NAVIG
Page 404 and 405: CHAPTER 13 ■ SENDING MESSAGESFigu
Page 406 and 407: CHAPTER 13 ■ SENDING MESSAGESmeth
Page 408 and 409: CHAPTER 13 ■ SENDING MESSAGESJava
Page 410 and 411: CHAPTER 13 ■ SENDING MESSAGESqueu
Page 412 and 413: CHAPTER 13 ■ SENDING MESSAGESAdmi
Page 414 and 415: CHAPTER 13 ■ SENDING MESSAGESTabl
Page 416 and 417: CHAPTER 13 ■ SENDING MESSAGESA se
Page 418 and 419: CHAPTER 13 ■ SENDING MESSAGESProp
Page 420 and 421: CHAPTER 13 ■ SENDING MESSAGESMess
Page 422 and 423: CHAPTER 13 ■ SENDING MESSAGESlist
Page 424 and 425: CHAPTER 13 ■ SENDING MESSAGESSett
Page 426 and 427: CHAPTER 13 ■ SENDING MESSAGESAt t
Page 428 and 429: CHAPTER 13 ■ SENDING MESSAGES@Mes
Page 430 and 431: CHAPTER 13 ■ SENDING MESSAGESDepe
Page 436 and 437: CHAPTER 13 ■ SENDING MESSAGESthe
Page 438 and 439: CHAPTER 13 ■ SENDING MESSAGES3.0.
Page 440 and 441: CHAPTER 13 ■ SENDING MESSAGESRunn
Page 442 and 443: CHAPTER 14 ■ SOAP WEB SERVICESFig
Page 444 and 445:
CHAPTER 14 ■ SOAP WEB SERVICESTra
Page 446 and 447:
CHAPTER 14 ■ SOAP WEB SERVICESpru
Page 448 and 449:
CHAPTER 14 ■ SOAP WEB SERVICESJav
Page 450 and 451:
CHAPTER 14 ■ SOAP WEB SERVICESFig
Page 452 and 453:
CHAPTER 14 ■ SOAP WEB SERVICES@Xm
Page 454 and 455:
CHAPTER 14 ■ SOAP WEB SERVICESWhe
Page 456 and 457:
CHAPTER 14 ■ SOAP WEB SERVICESThe
Page 458 and 459:
CHAPTER 14 ■ SOAP WEB SERVICESJav
Page 460 and 461:
CHAPTER 14 ■ SOAP WEB SERVICES•
Page 462 and 463:
CHAPTER 14 ■ SOAP WEB SERVICES@We
Page 464 and 465:
CHAPTER 14 ■ SOAP WEB SERVICESThe
Page 466 and 467:
CHAPTER 14 ■ SOAP WEB SERVICESWeb
Page 468 and 469:
CHAPTER 14 ■ SOAP WEB SERVICESPut
Page 470 and 471:
CHAPTER 14 ■ SOAP WEB SERVICES2.2
Page 472 and 473:
CHAPTER 14 ■ SOAP WEB SERVICESFig
Page 474 and 475:
CHAPTER 14 ■ SOAP WEB SERVICES448
Page 476 and 477:
CHAPTER 14 ■ SOAP WEB SERVICESapp
Page 478 and 479:
CHAPTER 15 ■ RESTFUL WEB SERVICES
Page 480 and 481:
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Page 490 and 491:
Page 492 and 493:
Page 494 and 495:
Page 496 and 497:
Page 498 and 499:
Page 500 and 501:
Page 502 and 503:
Page 504 and 505:
Page 506 and 507:
Page 508 and 509:
Page 510 and 511:
Page 512 and 513:
■ INDEXApache Maven. See Mavenapp
Page 514 and 515:
■ INDEXCD-BookStore application (
Page 516 and 517:
■ INDEXDerby, 31-32installing, 32
Page 518 and 519:
■ INDEXexpression language (EL),
Page 520 and 521:
■ INDEX tag, 328, 356 tag (JSF),
Page 522 and 523:
■ INDEXJava Archive (jar) files,
Page 524 and 525:
■ INDEXjavax.persistence.EntityMa
Page 526 and 527:
■ INDEXMessageConsumer, 394@Messa
Page 528 and 529:
■ INDEX tag, 176persistent class,
Page 530 and 531:
■ INDEX■ Sscalar expressions in
Page 532 and 533:
■ INDEXtimer service, 230-35autom
Page 534:
■ INDEXXHTML 1.0 Transitional, 30
show all

Beginning Java EE 6 with GlassFish 3, Second Edition

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?