Spring Roo
  1. Spring Roo
  2. ROO-674

Spring Roo 1.0.2 DB2 trailing space in driver class name prevents its loading.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Complete
    • Affects Version/s: 1.0.2.RELEASE
    • Fix Version/s: 1.1.0.M1
    • Component/s: @ CORE
    • Labels:
      None

      Description

      Spring Roo v1.0.2 add a trailing space to the database.properties database.driverClassName=com.ibm.db2.jcc.DB2Driver when setting DB2 as database in persistence setup preventing to load Driver class at compile time and runtime.
      This issue is visible when launching maven with trace enabled (-e switch) reading the Driver class name it is looking for ("...DB2Driver ")

        Activity

        Hide
        Alan Stewart added a comment -

        Fix available in SVN rev 680

        Show
        Alan Stewart added a comment - Fix available in SVN rev 680
        Hide
        Javier Beneito Barquero added a comment -

        Please note that, in spite that this seems to be a minor bug, you could expend a lot of time trying to figure out why the Tests fail due to ClassNotFoundException when you really know that it exists.

        Show
        Javier Beneito Barquero added a comment - Please note that, in spite that this seems to be a minor bug, you could expend a lot of time trying to figure out why the Tests fail due to ClassNotFoundException when you really know that it exists.
        Hide
        Alan Stewart added a comment -

        I don't follow. Please provide more information

        Show
        Alan Stewart added a comment - I don't follow. Please provide more information
        Hide
        Javier Beneito Barquero added a comment -

        Since this bug is already resolved, my last comment has no sense.

        What I meant is that you could expend a lot of time debugging a "ClassNotFoundException ibm.DB2Driver" when testing, but the actual problem is not the lack of that class, but the extra whitespace in the database.driverClassName line within the database.properties file.

        Thanks for resolving.

        Show
        Javier Beneito Barquero added a comment - Since this bug is already resolved, my last comment has no sense. What I meant is that you could expend a lot of time debugging a "ClassNotFoundException ibm.DB2Driver" when testing, but the actual problem is not the lack of that class, but the extra whitespace in the database.driverClassName line within the database.properties file. Thanks for resolving.

          People

          • Assignee:
            Alan Stewart
            Reporter:
            eltardo
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2m
              2m
              Remaining:
              Remaining Estimate - 2m
              2m
              Logged:
              Time Spent - Not Specified
              Not Specified