As of Hibernate 3.6, JDK 1.4 support has been dropped and the Hibernate
Annotations have been merged back into Core.
Then why should I need hibernate annotations on my pom.xml ??
On Sat, Feb 26, 2011 at 2:03 AM, Josh Canfield joshcanfi...@gmail.comwrote:
Could not initialize class
On Sat, 26 Feb 2011 09:52:40 -0300, dwi ardi irawan
penyihirke...@gmail.com wrote:
As of Hibernate 3.6, JDK 1.4 support has been dropped and the Hibernate
Annotations have been merged back into Core.
Then why should I need hibernate annotations on my pom.xml ??
You shouldn't. Have you
Yes, I've checked it. And it doesn't corrupt at all.
I think the problem is in the jetty launcher, cos when use mvn jetty:run, it
doesn't show any error
Strange
but now there is another problem, now, the page is show:
There is no data to display.
my table has only 1 row.
On Sat, Feb 26,
Yay. I got it works !
I forgot to mapped the beans entity on my hibernate configuration
hibernate-configuration
session-factory
property
name=hibernate.connection.driver_classcom.mysql.jdbc.Driver/property
property
One more question why it still show this error if I use jetty launcher(It
works fine if I use mvn jetty:run)
*Exception constructing service 'ValueEncoderSource': Error invoking service
builder method
org.apache.tapestry5.services.TapestryModule.buildValueEncoderSource(Map,
InvalidationEventHub)
Could not initialize class
org.hibernate.annotations.common.reflection.java.JavaReflectionManager
It looks like you need to add a dependency to hibernate annotations.
Josh
On Fri, Feb 25, 2011 at 10:26 AM, dwi ardi irawan
penyihirke...@gmail.com wrote:
I'm using Tapestry 5.2.4 and Hibernate
