• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

container managed relationship?

Ranch Hand
Posts: 130
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am stuck with this part of CMRelationship...
what I understand from page 396, HFEJB is-> in the ejbcreate()I have 5 fields of which 4 are inserted into the database and for the 5th one I wait till ejbPostCreate() and do a setDirector(dir)....by doing so what did the database get as the 5th field( ie how did the directorID get into the database ?)
Ranch Hand
Posts: 775
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You'll definitely drive yourself crazy if you are hoping this will be clear from the ejb-jar.xml descriptor content. The real mechanics are container-specific, and much clearer with some containers like JBoss.
As far as ejb-jar.xml and the bean callback methods are concerned, you can think of it like this:
0. before ejbCreate, the container doesn't know the pk
of the new entity.
1. ejbCreate() populates the data for the current entity,
including the fields necessary to define the pk, but
excluding any CMR foreign-key references.
2. After ejbCreate, but before ejbPostCreate, the container
knows the pk for your new entity.
3. ejbPostCreate() deals both with storing foreign keys
into your new entity, *and* providing your pk as a
foreign key value to other entities (remember, your
deployment descriptor might specify that the relationship
is navigable in both directions).
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic