At 03:07 PM 28/10/99 +0200, Albert Brotzer wrote:
>Sorry, this is not an answer to your problem. But we have a similar problem.
>An SQLException occurs during the update of an entity bean, because the
>record has been locked by an other user in the database. The Exception can
>be seen in the server trace output as a java.sql.SQLException, but neither
>the session bean nor the client get the RemoteException. They still believe
>everything went ok.
I don't believe that a RemoteException hsould be thrown for this sort of
error. If a method in your bean (entity or session) throws an application
exception (in this case SQLException) then that exception is propigated
back to the client.
I use this a lot when a session bean's business rules are violated, it
throws back an application exception to let the client know that there
was a business error.
Can you post some code, it would help us ...
--
Subvert the dominant paradigm
http://www.cyber4.org/members/grumpy/index.html
