• 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
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Shocked about CMR and only local component interfaces

 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
 
Evacuate the building! Here, take this tiny ad with you:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic