Include stack trace of unexpected exception when verifying if an object is valid for save

The current message is not very useful.

``` java
java.lang.AssertionError: 
Expected: valid for save enterprise object
     but got: java.lang.NullPointerException: null
```

We can make it a lot better if the stack trace of the `NullPointerException` is included.
