| Summary: | Implicit commit using StoredFunctionCall | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Emil Egredzija <emil.egredzija> | ||||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||||
| Status: | RESOLVED INVALID | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P2 | CC: | jamesssss, tom.ware | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Emil Egredzija
Created attachment 179608 [details]
java class which uses StoredFunctionCall
this is the source of java class where StoredFunctionCall is being used
Created attachment 179609 [details]
PLSQL function
PLSQL function which is called by JPA and it inserts data
Setting target and priority. See the following page for details of the meanings of these: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines This is not a bug, your code is wrong. Executing using the ServerSession is always auto-committed. You need to execute in the EntityManager/UnitOfWork. Query query = db.entManager.unwrap(JpaEntityManager.class).createQuery(query); The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |