Details

    • Type: Service Pack Request
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: No Version
    • Fix Version/s: 4.0
    • Component/s: Installer
    • Labels:
      None
    • ACT Numbers:

      13037

      Description

      Enterprise 3.x / H2 Database Functionality

      In activities-SqlMapConfig.xml, the sqlMap resources are keyed by the configured Hibernate dialect. During development, we use the embedded H2 database because it is superior to Derby and HSQL.

      Since there are no iBatis mappings for the H2Dialect, we have to override activities-SqlMapConfig.xml and replace the $

      {hibernate.dialect} with a hard-coded one (derby works).

      It would be convenient if there was a way to override the iBatis mapping independent of the hibernate dialect used, by simply setting some property.



      Changed to Contribution the 20/10/2009



      Customer has done the following to overcome the situation:

      activities-feed-context.xml:

      - add a PropertyPlaceholderConfigurer with custom-hibernate-dialect.properties as property source
      - add property to sqlMapClient:
      <property name="sqlMapClientProperties">
      <props>
      <prop key="ibatis.dialect">${ibatis.dialect}</prop >
      </props>
      </property>


      activities-SqlMapConfig.xml:
      - replace ${hibernate.dialect}

      with $

      {ibatis.dialect}

      custom-hibernate-dialect.properties:

      • add line ibatis.dialect=$ {hibernate.dialect}

      I can now re-assign ibatis.dialect to something different without having to patch anything.

        Activity

        Hide
        buddycasino Michael Böckling (Inactive) added a comment -

        Proposed solution: add an additional indirection property, like this:

        ibatis.dialect = $

        {hibernate.dialect}

        That way, the current behaviour would be preserved, but could be easily overridden if desired.

        Show
        buddycasino Michael Böckling (Inactive) added a comment - Proposed solution: add an additional indirection property, like this: ibatis.dialect = $ {hibernate.dialect} That way, the current behaviour would be preserved, but could be easily overridden if desired.
        Hide
        mrogers Mark Rogers added a comment -

        We no longer support these databases or Hibernate for that matter.

        Show
        mrogers Mark Rogers added a comment - We no longer support these databases or Hibernate for that matter.

          People

          • Assignee:
            closedissues Closed Issues
            Reporter:
            aevans Anthony Evans
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: