Best practices about throwing exceptions from a remote service exposed via Spring's HTTP Invoker?

Besides RemoteException and all of his subclases thro开发者_如何学编程wn for non business logic problems, what is the right way to handle business related exceptions? Is it OK to subclass RuntimeException in those cases? Should I keep my business exceptions being non-checked?

I believe business logic exceptions are actually the only justified case for the checked exceptions, unlike lower level connectivity, database, file access, etc. exceptions.