| Author |
local and remote home interfaces
|
Murali Krishna M
Greenhorn
Joined: Nov 11, 2004
Posts: 2
|
|
I am a new bee learning EJB. Going through Head First Ejb. I could not understand, why the client code should always know whether it is accessing a local bean or a remote bean. Why the EJB technology leave this decision to the client at the development level itself? Shouldn't it be at least configured at deployment lever or client should bother nothing at all. I have worked on distributed systems where the client need not be aware of the service provider location for any reason. I may be missing some thing. Could some one explain or provide any links.
murali
|
Start by doing what is necessary; then do what is possible. Suddenly you are doing the impossible. -St.Francis
|
 |
Nathaniel Stoddard
Ranch Hand
Joined: May 29, 2003
Posts: 1258
|
|
|
There's always a transport aspect of distributed systems ... what do you do when the remote system is unavailable? Etc. There are design patterns you could use to abstract away the locality issue if your application really needed to do that.
|
Nathaniel Stodard<br />SCJP, SCJD, SCWCD, SCBCD, SCDJWS, ICAD, ICSD, ICED
|
|
 |
|
|
subject: local and remote home interfaces
|
|
|
0
