Shocked about CMR and only local component interfaces
posted 12 years ago
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.