As Pradeep says, it is definitely possible, though it happens in less cases than you may think. For the most part code written for local clients is not coarse-grained enough to be used as for remote clients. Therefore, I rarely find the need to write an
ejb to support both. In fact, I don't typically find the need to write ejbs that are remoteable at all since I always try to co-located the web tier whenever possible.
Regardless, the problem that some people have in this respect is that I still see
alot of ejb code which throws RemoteExceptions from the Bean Implementation class. Since local interfaces are not allowed to throw RemoteExceptions the developers then run into trouble deploying the ejbs. Other than that it is a fairly straight-forward exercise to implement both types of interfaces.
[ August 27, 2003: Message edited by: Chris Mathews ]