Feed on

Holy Old Guys, Batman!  It’s GeePawHill and he’s back inna house with the second DoubleDawgDare episode!

This one’s a simple one, so there’s only ‘after’ code, just below the video.  No matter, the good news is from here on out we’re going to be able to move at the speed of thought!

Get the Flash Player to see this content.

The After Code for Step 1 (1534)

6 Responses to “DoubleDawg 1: A Quick Tour”

  1. […] has an excellent series of posts going on down at the creek, and in this one he said something which struck a chord.  He cleaned up all the warnings in a class to ensure that […]

  2. Jeff Grigg says:

    Could you export your GeePawHill eclipse formatter (to XML) and upload it, to make it available to us students of knowledge who are following along?


  3. Jeff Grigg says:

    The public “resolvePropertyName” method bugs me. I so want to make it static.

    So I did some digging. Turns out the exact same code is in a public static method in the “AnnotationUtils” class. It’s used by the XWorkConverter class.

    Quick change:
    “ResolvePropertyName(…)” to “AnnotationUtils.resolvePropertyName(…)”.
    Then I run all of my new tests for AnnotationValidationConfigurationBuilder. They all pass. Then I delete the method from AVCB, and the two static constants.

    Now AnnotationValidationConfigurationBuilder has only a single public method. And it’s the method that does the real work of the class.

    • GeePawHill says:

      I also saw that static. The best local fix is the one you did. I wonder if it’s called from all over? It may not even be used elsewhere.
      — GeePawHill

      • Jeff Grigg says:

        I checked: The “AnnotationUtils.resolvePropertyName(…)” is called from only one place (class XWorkConverter). …until we change our code to call it. Then it’s called from two places.

        Code reuse in action!!! ;->

Leave a Reply

AWSOM Powered