Just lookin' for some quick design ideas from the experts. I am working on a
project where I have an applet that communicates with a server by serializing
objects to a servlet. The servlet does the work, and then writes the results
back to the applet. Pretty straightforward...

What I am curious about is how best to handle business logic errors. I am
considering just creating an exception and serializing that to the applet.
My communication layer class could then just throw the exception in the
client. I have done some testing, and it seems to work just fine - ie.
it's legal, but is it moral? Is this a reasonable solution, or is there a
better way of handling things?