PeopleSoft Adoption Made Smooth & Simple!
On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool. Claim Your Free WalkMe Account Now
Course Of The Month
7 days, 7 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
JPA Master-Detail Rollback Problem
Posted on 2012-03-21
Hello everbody,
Normally, inserting master-detail object to database follow these steps.
1- insert master to database cache.
When error occurred, do rollback.
2- insert detail to database cache.
When error occurred, do rollback.
3-if no error, commit transaction.
But in jpa transaction rollback is not working same, I think.
I have two objects to persist. Like these:
KeyOption optionValue is unique in database.
When I call jpa persist I have trouble with these object. JPA insert ConditionKey to database cache. KeyOption optionValue is unique. When I insert already inserted optionValue
JPA throw en UniqunessException but ConditionKey is already changed. But database not.
How can I solve these rollback problem in JPA? (EclipseLink)
public void insertConditionKey(Conditi
EntityManager em = entityManagerFactory.creat
try {
em.getTransaction().begin(
em.persist(conditionKey);
em.flush();
em.getTransaction().commit
} catch (Exception e) {
if (em.getTransaction().isAct
em.getTransaction().rollba
}
throw e;
} finally {
em.close();
}
}
Normally, inserting master-detail object to database follow these steps.
1- insert master to database cache.
When error occurred, do rollback.
2- insert detail to database cache.
When error occurred, do rollback.
3-if no error, commit transaction.
But in jpa transaction rollback is not working same, I think.
I have two objects to persist. Like these:
public class ConditionKey implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE)
@Column(name = "KEY_ID")
private Integer keyId;
@OneToMany(mappedBy = "conditionKey", fetch = FetchType.EAGER, cascade = CascadeType.ALL, orphanRemoval = true)
private List<KeyOption> keyOptions;
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE)
@Column(name = "KEY_ID")
private Integer keyId;
@OneToMany(mappedBy = "conditionKey", fetch = FetchType.EAGER, cascade = CascadeType.ALL, orphanRemoval = true)
private List<KeyOption> keyOptions;
@Entity
@Table(name = "KEY_OPTION")
public class KeyOption implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE)
@Column(name = "KEY_OPTION_ID")
private Integer keyOptionId;
@Column(name = "OPTION_VALUE")
private String optionValue;
@ManyToOne(fetch = FetchType.EAGER)
@JoinColumn(name = "KEY_ID")
private ConditionKey conditionKey;
@Table(name = "KEY_OPTION")
public class KeyOption implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE)
@Column(name = "KEY_OPTION_ID")
private Integer keyOptionId;
@Column(name = "OPTION_VALUE")
private String optionValue;
@ManyToOne(fetch = FetchType.EAGER)
@JoinColumn(name = "KEY_ID")
private ConditionKey conditionKey;
KeyOption optionValue is unique in database.
When I call jpa persist I have trouble with these object. JPA insert ConditionKey to database cache. KeyOption optionValue is unique. When I insert already inserted optionValue
JPA throw en UniqunessException but ConditionKey is already changed. But database not.
How can I solve these rollback problem in JPA? (EclipseLink)
public void insertConditionKey(Conditi
EntityManager em = entityManagerFactory.creat
try {
em.getTransaction().begin(
em.persist(conditionKey);
em.flush();
em.getTransaction().commit
} catch (Exception e) {
if (em.getTransaction().isAct
em.getTransaction().rollba
}
throw e;
} finally {
em.close();
}
}
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Basic understanding on "OO- Object Orientation" is needed for designing a logical solution to solve a problem. Basic OOAD is a prerequisite for a coder to ensure that they follow the basic design of OO. This would help developers to understand the b…
When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
Viewers learn about the “for” loop and how it works in Java. By comparing it to the while loop learned before, viewers can make the transition easily. You will learn about the formatting of the for loop as we write a program that prints even numbers…
Viewers will learn about arithmetic and Boolean expressions in Java and the logical operators used to create Boolean expressions. We will cover the symbols used for arithmetic expressions and define each logical operator and how to use them in Boole…
Suggested Courses
Course of the Month7 days, 7 hours left to enroll
728 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.