#71 allowed-exceptions not working for default mappings

closed
None
5
2007-04-04
2007-02-13
No

Hi Matt,
I was able to verify that the allowed-exceptions still works for me provided a supply a mapping in the dozerBeanMapping file. My domain object that throws the business runtime exception seems to require a mapping between it and the data transfer object it represents. That is, if I don't specify this mapping explicitly, the 2 classes get mapped OK (all the fields get copied) but the allowed-exceptions are ignored. I traced through and could see that without a mapping, the classMap containing the allowed-exceptions is empty (at line 314 of the 3.0 MappingProcessor) and thus the exception is not getting thrown. I didn't go beyond this to see why though.

Is this meant to be a feature, that one has to supply a mapping between 2 classes to get allowed exceptions thrown ?

Great work on 3.0, and thanks for including our patches!

Cheers
Alan

Discussion

  • Matt Tierney

    Matt Tierney - 2007-04-01

    Logged In: YES
    user_id=1236069
    Originator: YES

    I fixed this. Nice find!

     
  • Matt Tierney

    Matt Tierney - 2007-04-01
    • assigned_to: nobody --> mhtierney
    • status: open --> pending
     
  • Matt Tierney

    Matt Tierney - 2007-04-04
    • status: pending --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks