ansaurus

Question

Wicket, Spring and Hibernate - Testing with Unitils - Error: Table not found in statement [select relname from pg_class]

Answer 1

+1 A:

While applicationContext-test.xml overrides the default datasource to supply a Unitils datasource, the applicationContext.xml still declares the following property (that gets replaced during Maven filtering):

<prop key="hibernate.dialect">${hibernate.dialect}</prop>

So, if you want to run integration tests against an HSQLDB database (Unitils seems to be configured to do so), my understanding is that you are supposed to use the filter filters-LOCAL.properties that is triggered when using the LOCAL profile and declares:

hibernate.dialect=org.hibernate.dialect.HSQLDialect

You can check the target/classes/applicationContext.xml to confirm this but it seems obvious that you're not getting the above value but PostgreSQLDialect.

The odd part is that the pom.xml of mysticpaste declares the LOCAL profile as activeByDefault (at least the version in the project repository):

<profile>
  <id>LOCAL</id>
  <activation>
    <activeByDefault>true</activeByDefault>
  </activation>
  <properties>
    <env>LOCAL</env>
  </properties>
</profile>

It should just work. So the question are:

what does mvn help:active-profiles say?
do you have the this LOCAL profile (and the LOCAL filter)?
do you have the latest version of this pom.xml?

Pascal Thivent 2010-05-04 18:24:15

I have removed the filters that mysticpaste uses in their pom, so I'm not using it. I did this based on an earlier question where it was suggested that I keep away from using filters. Instead of these filters I'm using 1 single application.properties file (which contains "hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect").I'll create the LOCAL filter as you suggested with the appropriate HSQLDialect set :-)

John 2010-05-04 18:32:20

The suggestion you received here on SO is just one opinion and doesn't necessarily reflect all opinions :) I personally share the point of view expressed by the author of this Wicket series in [this comment](http://www.mysticcoders.com/blog/2009/03/09/5-days-of-wicket-day-1/#comment-1313) and prefer profiles over `PropertyPlaceholderConfigurer`.

Pascal Thivent 2010-05-04 18:41:37

Thanks a lot Pascal, for the help with the original problem and the note on the use of profiles. Your suggestion of making a profile with the appropriate dialect seems to have done the trick!

John 2010-05-04 18:46:12

@John To be clear, using a profile to switch from one dialect to another is just one way to go, nothing forces you to use this solution (even if I think profiles are nice). But the fact is that you need to change the value of the `hibernate.dialect` property depending on the environment.

Pascal Thivent 2010-05-04 19:26:57

@Pascal Using profiles seems like a clever choice as I do have several environments (development, testing, pre-production and production). When deploying to the production server, is it enough to use the -P parameter for the deploy command only, or would I need to set the profile containing my production settings to activeByDefault before sending it off to tomcat?

John 2010-05-05 05:40:27

@John: Dealing with environments is indeed a perfect use case for profiles. Regarding your question, my recommendation would be to not change the `activeByDefault`, use this for the profile that you use the most frequently (very likely a development profile), don't change your pom to release to another environment. Instead, use `-P` when you want another profile (this will disable any profile active by default). Just in case, have a look at the [Introduction to Build Profiles](http://maven.apache.org/guides/introduction/introduction-to-profiles.html).

Pascal Thivent 2010-05-05 06:12:41

ansaurus

tags:

views:

answers:

Wicket, Spring and Hibernate - Testing with Unitils - Error: Table not found in statement [select relname from pg_class]

related questions