1 Reply Latest reply on Dec 11, 2005 11:26 AM by James Moring

    Exception thrown as a result of @Version concurrency violati

    James Moring Newbie

      Shouldn't this be a specfic exception class as in OptimisticConcurrencyViolation or something to that effect. The generic throwing of EJBException with a message detailing the violation makes this more difficult to handle (Parse message for key words "Row was Updated"????) . Most exception get packed up and sent back to the client with some vague message about contacting support... but this error can actually be handled gracefully.

      Am I missing something?