BIND 10 #3048: Remove log messages from ServerHooks methods used during hook registration

[BIND 10 Development]

#3048: Remove log messages from ServerHooks methods used during hook registration
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  dhcp          |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-DHCP-20130717
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by stephen):

 * owner:  stephen => UnAssigned
 * status:  accepted => reviewing


Old description:

> One technique recommended for initializing the list of hooks in a server
> involves the use of static initialization functions.  However, the
> presence of logging messages in the ServerHooks constructor and
> registerHooks() method prevents this because logging is not initialized
> at this stage.
>
> This ticket removes two messages (one a debug message and one a warning
> message) to allow the technique to work.

New description:

 One technique recommended for initializing the list of hooks in a server
 involves the use of static initialization functions.  However, the
 presence of logging messages in the !ServerHooks constructor and
 registerHooks() method prevents this because logging is not initialized at
 this stage.

 This ticket removes two messages (one a debug message and one a warning
 message) to allow the technique to work.

--

Comment:

 Ready for review.  The first commit makes the changes to the code.  The
 second is a cosmetic change, reordering the message file into alphabetical
 order.

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