why not remove remote / local interfaces in ejb

Discussions

EJB programming & troubleshooting: why not remove remote / local interfaces in ejb

  1. why not remove remote / local interfaces in ejb (1 messages)

    just curious... why we don't specify a ejb being "remote / local" in the deployment descriptor?

    i know the advantages on having the remote and local interface will allow us to expose only certain methods of the bean, but there are always "public / protected / private", how about if we can specify that in the deployment descriptor also.

    it adds a lot more works for having to update the remote / local interface, don't even have to describe the *business delegate* if you have that. without some decent IDEs, everytime you update anything on the bean, you have to update those interfaces also.

    sometime it's really a pain to do so...
  2. Then how would you deal with RemoteExceptions? I think the decision was based on the fact that network calls are very different from local ones (different classes of errors, performance implications of network access, etc.).

    --Steven