Issue Type: Feature Request Feature Request
Assignee: Unassigned
Created: 13/Aug/13 3:30 AM
Description:

When starting the PushEE/UnifiedPush server, Hibernate is generating a few ERRORs, while creating/updating the tables:

2013/08/13 02:14:50,016 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-1) HHH000388: Unsuccessful: create table Developer (id bigint not null, newPassword varchar(255), password varchar(255), role varchar(255), primary key (id))
2013/08/13 02:14:50,018 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-1) Table 'Developer' already exists
2013/08/13 02:14:50,660 INFO  [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-1) HHH000232: Schema update complete
2013/08/13 02:14:50,779 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-2) HHH000388: Unsuccessful: create table hibernate_sequence ( next_val bigint )
2013/08/13 02:14:50,781 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-2) Table 'hibernate_sequence' already exists
2013/08/13 02:14:50,783 INFO  [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-2) HHH000232: Schema update complete

The reason for this is that the 'Developer' class/entity is present in BOTH persistence units.
Project: AeroGear Push
Priority: Major Major
Reporter: Matthias Wessendorf
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira