• 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 ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

about ejb relationship

 
Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can the bean provider manipulate ejb relationships at run time.. if so, how ??

And what does this really means !!!

Also, what does it mean by saying "CMR can only exists among entity beans with the same LOCAL RELATIONSHIP SCOPE "
[ August 05, 2004: Message edited by: Giju George ]
 
Author & Gold Digger
Posts: 7617
6
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can the bean provider manipulate ejb relationships at run time.. if so, how ??
Yes of course. As an example, let's say you have two entity beans, Customer and BankAccount which have the following relationship:

Customer 1 <-----------------> * BankAccount

One Customer can have 0 or many BankAccount for which he is the sole owner.
At some point the customer may decide to create a new bank account for some reason.

Basically, invoking customerBeanLocal.addBankAccount(someNewBankAccountLocal) would do the job.

Also, what does it mean by saying "CMR can only exists among entity beans with the same LOCAL RELATIONSHIP SCOPE "
It means that the entity beans that share relationships together must provide a local component interface and must have been deployed in the same EJB container on the same physical server.
 
No more fooling around. Read this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic