Hmmm, the command is a session bean and you have to use remote interface to call Execute? Not something I'd do, I think.
Yeah, any of these would be more common:
* Execute a command on the client which may or may not do remote calls to EJB servers. That's just part of client design. The server knows nothing about commands.
* Pass a POJO command to the server which then executes the command. Client and server both have dependencies on the command.
* Pass a key to the server which maps the key to a command and executes the command. Only the server has a dependency on the command. The
servlet spec is pretty much this.
Waddya think?