• 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 ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Shocked about CMR and only local component interfaces

 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just to ensure I get this right ....
If you want to use CMR, then you have to go with local coponent interfaces on entity beans - right ?
Now I know that handing Entity beans to clients might be a performance issue, and that you better hide stuff using the Facade pattern.
BUT .... This makes the design still very inflexible, and you have to build a facade for basically each situation where Entity beans are involved.
OR ... if you dont want that you have to build both a remote and local component interface, which also is kind of overhead.
Is one of you folks able to tell me
a) why this restriction exists ?
b) If this restriction still exists in J2EE 1.4 ?
This is likely the first thing with EJBs I really have a problem with - that's why I at least want to understand the reasoning behind.
 
When people don’t understand what you are doing they call you crazy. But this tiny ad just doesn't care:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic