Details

    • Type: Improvement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.3.0
    • Component/s: None
    • Labels:
      None

      Description

      I would like to invert the current preprocessor behaviour.
      Currently we got jdk1.3 compliant classes that are mungled for jdk1.4+ at build time.
      I think that it would be better to have "official" jdk1.4+ classes and mungle them at runtime when we don't have jdbc3 in the classpath.

      More: i don't have a jdk1.3 installed right now but looking the code it seems that the jdk1.4 version would work with jdk1.3 too (the inverse is not true).

      I already changed my local code, so if noone dislike the change I will apply it later.

        Activity

        Hide
        bago Stefano Bagnara added a comment -

        This should work as like as before. Now the default is jdbc3 compliance.

        Show
        bago Stefano Bagnara added a comment - This should work as like as before. Now the default is jdbc3 compliance.
        Hide
        danny@apache.org Danny Angus added a comment -

        Closing issue fixed in released version.

        Show
        danny@apache.org Danny Angus added a comment - Closing issue fixed in released version.

          People

          • Assignee:
            bago Stefano Bagnara
            Reporter:
            bago Stefano Bagnara
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development