Well, It looks like the tapestry-hibernate pom.xml was changed and <scope>provided</scope> was removed from the hibernate dependency. Which suddenly brought in 3.2.2.ga which of course doesn't include the Oracle10gDialect. Is this a mistake?
Explicitly excluding org.hibernate hibernate solved the problem. I couldn't find any reference to this in the Tapestry JIRA but will log an issue if necessary . Paudi <!-- The Hibernate dependencies are provided; which gives the final application the ability to choose the appropriate version. Further, in many cases (such as JBoss deployment), they are, in fact, provided by the container. For a Tomcat deployment, you're more likely to include the hibernate JARs and dependencies inside the WAR. --> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate</artifactId> <version>3.2.2.ga</version> <exclusions> <exclusion> <groupId>javax.transaction</groupId> <artifactId>jta</artifactId> </exclusion> </exclusions> </dependency> On 04/07/2008, Patrick Moriarty <[EMAIL PROTECTED]> wrote: > > Hi, > > After switching to 5.0.13, I can't start my Tapestry + Spring [2.5.4] + > Hibernate [3.2.6.ga] application with any oracle dialect other than > Oracle9Dialect, which is now deprecated. > > Funny enough, the deprecation warning, present when using 5.0.12 with > Oracle9Dialect, is no longer showing! > > Any ideas on what could be happening? > > Paudi >
