Hi, Although the error in the calendar users, rooms, and files were transferred. I have not tested in 3.0.1 or snapshot. But I tested it on 2.1.1 and it only restored users, losing the other data. I did not wrote down the error this time.
2014-04-14 3:33 GMT-03:00 Maxim Solodovnik <[email protected]>: > Am I right thinking: > 1) backup was successful > 2) you have error while restoring? > > Is it reproducible in 3.0.1? > can you send me backup ASAP privately so I can include the fix into upcoming > 3.0.1-RELEASE or 3.0.2-SNAPSHOT? > > > On Sun, Apr 13, 2014 at 7:40 PM, Jaime Balbino <[email protected]> wrote: >> >> Hi, >> I need backup OM 2.0 user and files for OM 3.0 but I have this error >> (in GUI or admin.sh command): >> >> org.springframework.dao.InvalidDataAccessApiUsageException: >> Encountered new object in persistent field >> "org.apache.openmeetings.db.entity.calendar.Appointment.room" during >> attach. However, this field does not allow cascade attach. Set the >> cascade attribute for this field to CascadeType.MERGE or >> CascadeType.ALL (JPA annotations) or "merge" or "all" (JPA orm.xml). >> You cannot attach a reference to a new object without cascading.; >> nested exception is <openjpa-2.2.2-r422266:1468616 nonfatal user >> error> org.apache.openjpa.persistence.ArgumentException: Encountered >> new object in persistent field >> "org.apache.openmeetings.db.entity.calendar.Appointment.room" during >> attach. However, this field does not allow cascade attach. Set the >> cascade attribute for this field to CascadeType.MERGE or >> CascadeType.ALL (JPA annotations) or "merge" or "all" (JPA orm.xml). >> You cannot attach a reference to a new object without cascading. >> FailedObject: org.apache.openmeetings.db.entity.room.Room@1d657b9 >> >> How do I make? > > > > > -- > WBR > Maxim aka solomax
