]
Kris Verlaenen updated JBPM-3049:
---------------------------------
Fix Version/s: jBPM 5.1
Affects Version/s: jBPM 5.0
(was: jBPM 5.2)
JPAWorkingMemoryDbLogger.updateProcessLog uses hard coded query
(likely hibernate specific)
-------------------------------------------------------------------------------------------
Key: JBPM-3049
URL:
https://issues.jboss.org/browse/JBPM-3049
Project: jBPM
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 5.0
Environment: OPENEJB 3.2, OPENJPA 2.0.1
Reporter: Jürgen Schmied
Assignee: Kris Verlaenen
Fix For: jBPM 5.1
in this function there is a hardcoded query string :
List<ProcessInstanceLog> result = getEntityManager().createQuery(
"from ProcessInstanceLog as log where log.processInstanceId = ? and
log.end is null")
.setParameter(1, processInstanceId).getResultList();
it gives the following error:
<openjpa-2.0.1-r422266:989424 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: "Encountered "from" at
character 1, but expected: ["DELETE", "SELECT",
"UPDATE"]." while parsing JPQL "from ProcessInstanceLog as log where
log.processInstanceId = ? and log.end is null". See nested stack trace for original
parse error.
Fix: use a named query and put it in orm.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: