That seems odd, you shouldn't need to use @SubModule; the necessary modules are automatically loaded if on the classpath.
On Fri, Oct 1, 2010 at 6:31 AM, Michal Gruca <michalgr...@gmail.com> wrote: > > I gave presentation about Tapestry yesterday. In it I included hibernate > integration example, I will share that after weekend. > From my observation: make sure that You have both hibernate libraries in > Your classpath. Double check did You annotated AppModule with > @Submodule(HibernateModule.class). That are two related points that gave me > a lot of trouble. Mainly because of eclipse weakest side: maven integration. > -- > View this message in context: > http://tapestry-users.832.n2.nabble.com/Early-steps-getting-Tapestry-and-Hibernate-working-via-DAO-tp5591178p5591360.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
