EntityImpl, Propogating Exceptions

Question

Hi,
Suppose that I have three entities, EntityA, EntityB and EntityC with Attribute Level and entity Level validation Rules. When I update EntityA I also update EntityB and EntityB triggers update of EntityC. When I remove EntityA, I remove EntityB and this triggers Update of EntityC. When I create EntityA, I also create EntityB and this triggers update of EntityC. If EntityC fails validation it does not throw the exception to the originating entities. But it tries to validate itself ten times and fails again. I can see a lot of validation messages on the screen. I wish that the failing entity throws that exception to its originating entity and so on. When no validation rule is broken everything works fine. When I implement validation rule of entityC on entityA via entity associations I get the desired behaviour. For updates and inserts I trigger change on prepareForDML method, sometimes use postChanges method to remove child entities and post its changes before parent. I appreciate your helps.
Best Regards,

Answer 1

NEVER CATCH AN EXCEPTION TO THROW ANOTHER EXCEPTIONThis depends on what you mean by Exception. If you mean never catch a java.lang.Exception just to throw another java.lang.Exception, then yes, I tend to agree.
If you mean never catch an exception just to throw another one, then I dont agree at all.
This is, in fact, good practise to provide implementation 'layers'.
E.g, if I have an data interface, and provide XML, SQL and flat file implementations, I certainly cant go throwing SQLExceptions thru the interface. Likewise, I dont want to throw just 'java.lang.Exception'.
So, I make an Exception type which has meaning at the interface level ('StorageException' for example).
In my SQL implementation, for example, I might then do this:
  try {
    someStatement.execute();
  } catch(SQLException e) {
    throw new StorageException("Failed to update customer", e);
  }