Pete Muir wrote:
>> * GroovyBooking example
>> - JBSEAM-3579
>> - Getting the sql error below. Jozef also saw this with Seam
>> 2.0.3.CR2 on AS 5 CR2
>> - Caused by: java.sql.SQLException: Violation of unique constraint
>> SYS_PK_49: duplicate value(s) for column(s) $$
>> - during import.sql import
> Are you sure you have a clean data dir?
Ok, this occurs because EJB3 is now deploying JPA for WARs
(persistence.xml in WEB-INF/classes/persistence.xml), so that Hibernate
gets started twice, and so import.sql is run twice. ALR, is it correct
that PUs get deployed from inside a war for EJB3? Other EE5 containers
don't do this.
Yes, @see comments in: