BIND 10 #2421: don't reject configuring entire inmemory datasrc due to one broken zone

[BIND 10 Development]

#2421: don't reject configuring entire inmemory datasrc due to one broken zone
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20121120
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  4
                   Keywords:         |           Total Hours:  0
            Defect Severity:  High   |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:7 muks]:
 > Back to review. It now handles `NullRRset`, `AddError` and `EmptyZone`
 exceptions.

 Not looking at the code, but I don't think it a good idea to catch
 each and every possible exception if the above means that.  I think we
 use this opportunity to make it a bit more maintainable: introducing
 some exception class hierarchy so we can distinguish minor errors for
 a specific zone and more serious errors.  The former should be caught
 per zone basis and can be basically ignored with a log message; the
 latter would need to be propagated to a higher level, and would either
 result in dropping the entire configuration or even terminate the
 program.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2421#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development