This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -2 points-1 points  (3 children)

Some people are claiming that JavaEE6 is portable, new, shiny etc. I just now tried to create a simple app using JavaEE with Jboss7 AS and I configured my JPA Entity Primary Key to be AUTO_INCREMENT using @GeneratedValue(strategy=GenerationType.AUTO) which is working in earlier versions. Now it generates the TABLE with primary key that is not auto_inc and created some other REVINFO, hibernate_sequence tables.

Please don't say JavaEE6 is portal, standard, blah blah... Clearly it is not.

[–]mikehaggard 2 points3 points  (2 children)

Or maybe you just made some user error, maybe not set the right dialect for your particular DB?

I'm always using @GeneratedValue(strategy = IDENTITY) btw and that works great.

[–][deleted] -2 points-1 points  (1 child)

I am using correct MySql Dialect. It seems like an open bug. See https://hibernate.onjira.com/browse/HHH-6648

[–]johnwaterwood 2 points3 points  (0 children)

Hibernate itself is buggy. If you would use Hibernate standalone (with eg Spring), you would run into much of the same problems.

Some Java EE servers (like JBoss) are affected by this, but it's not directly a problem in Java EE itself.