• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Jeanne Boyarsky
  • Bear Bibeault
  • Knute Snortum
  • paul wheaton
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Ganesh Patekar
  • Tim Holloway
  • Carey Brown
  • salvin francis

question about primary key in JPA

Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
mock question:

Which statement is true about the primary key of a Java Persistence entity?
A. The primary key cannot be overridden by a mapping descriptor.
B. The location of the primary key defines in the topmost entity class in the hierarchy.
C. If property-based access is used, the properties or the primary key class must be public or protected.
D. At least part of a primary key must be defined in the class that is the topmost class of an entity which is defined by a hierarchy of classes.

Given answer is C,primary key could be put in mapped superclass too,so B is wrong,D apparently wrong.
why A is wrong?
can anyone explain C(why property-based,why public or protected,and how about field-based access?)
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The reason for C is tat when you using property based access, the accessor methods(getter/setter) should be public or protected. It cant b private or default.
Always look on the bright side of life. At least this ad is really tiny:
create, convert, edit or print DOC and DOCX in Java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!