Beginning Java EE 6 with GlassFish 3, Second Edition

More documents

Recommendations

Info

CHAPTER 3 ■ OBJECT-RELATIONAL MAPPINGAs discussed previously, the @ElementCollection annotation is used to indicate the objects in themap that are stored in a collection table. The @CollectionTable annotation changes the default name ofthe collection table to TRACK.The difference with collections is the introduction of a new annotation: @MapKeyColumn. Thisannotation is used to specify the mapping for the key column of the map. If it is not specified, thecolumn is named with the concatenation of the name of the referencing relationship attribute and _KEY.Listing 3-28 shows the annotation renamed to POSITION from the default (TRACK_KEY) to be clearer.The @Column annotation indicates that the column containing the map value should be renamedTITLE. The result is shown in the Figure 3-4.Figure 3-4. Relationship between the CD and the TRACK tablesMapping with XMLNow that you are more familiar with elementary mapping using annotations, let’s take a look at XMLmapping. If you have used an object-relational framework such as Hibernate, you will be familiar withhow to map your entities in a separate XML deployment descriptors file. Since the beginning of thischapter, you haven’t seen a single line of XML, just annotations. JPA also offers, as an option, an XMLsyntax to map entities. I will not go into too much detail about the XML mapping, as I’ve decided tofocus on annotations (because they are easier to use in a book and most developers choose them overXML mapping). Keep in mind that every single annotation you see in this chapter has an XMLequivalent, and this section would be huge if I covered them all. I encourage you to check Chapter 12(XML Object/Relational Mapping Descriptor) of the JPA 2.0 specification, which covers all the XML tagsin more detail.XML deployment descriptors are an alternative to using annotations. However, although eachannotation has an equivalent XML tag and vice versa, there is a difference in that the XML overridesannotations. If you annotate an attribute or an entity with a certain value, and at the same time youdeploy an XML descriptor with a different value, the XML will take precedence.The question is, when should you use annotations over XML and why? First of all, it’s a matter oftaste, as the behavior of both is exactly the same. When the metadata is really coupled to the code (forexample, a primary key), it does make sense to use annotations, since the metadata is just anotheraspect of the program. Other kinds of metadata, such as the column length or other schema details, canbe changed depending on the deployment environment (e.g., the database schema is different in thedevelopment, test, or production environment). A similar situation arises when a JPA-based productneeds to support several different database vendors. Certain id generation, column options, etc. mayneed to be adjusted depending on the database type in use. This may be better expressed in externalXML deployment descriptors (one per environment) so the code doesn’t have to be modified.Let’s again turn to the Book entity example. This time imagine you have two environments, and youwant to map the Book entity to the BOOK table in the development environment and to theBOOK_XML_MAPPING table in the test environment. The class will only be annotated with @Entity (seeListing 3-29) and not include information about the table it should be mapped to (i.e., it will have no84
CHAPTER 3 ■ OBJECT-RELATIONAL MAPPING@Table annotation). The @Id annotation defines the primary key as being autogenerated, and a @Columnannotation sets the size of the description to 500 characters long.Listing 3-29. The Book Entity with Only a Few Annotations@Entitypublic class Book {@Id@GeneratedValue(strategy = GenerationType.AUTO)private Long id;private String title;private Float price;@Column(length = 500)private String description;private String isbn;private Integer nbOfPage;private Boolean illustrations;// Constructors, getters, setters}In a separate book_mapping.xml file (see Listing 3-30), following a specified XML schema, you canchange the mapping for any data of the entity. The tag allows you to change the name of thetable to which the entity will be mapped (BOOK_XML_MAPPING instead of the default BOOK). Inside the tag, you can customize the attributes, specifying not only their name and length, but alsotheir relationships with other entities. For example, you can change the mapping for the title columnand the number of pages (nbOfPage).Listing 3-30. Mapping the File META-INF/book_mapping.xml85
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: CHAPTER 1 ■ JAVA EE 6 AT A GLANCE
Page 67: CHAPTER 1 ■ JAVA EE 6 AT A GLANCE
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 149 and 150: C H A P T E R 4■ ■ ■Managing
Page 151 and 152: CHAPTER 4 ■ MANAGING PERSISTENT O
Page 161 and 162:
CHAPTER 4 ■ MANAGING PERSISTENT O
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:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369:
Page 372 and 373:
CHAPTER 12 ■ PROCESSING AND NAVIG
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
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 432 and 433:
Page 434 and 435:
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:
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:
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?