I'm of the school of thought that says that as long as business logic:
- lives in one place
- where it is properly documented
- proper access is provided through services that can be loosely coupled
- through a published abstracted interface
I don't care if the logic lives in a stored procedure, in a J2EE middle tier, in a clips expert system, or wherever. No matter where you store our business logic the "law of conservation of misery" is going to guarantee that someone will say it was the wrong idea because component/repository X needs to be swapped out for technology/method Y.
