[
https://jira.jboss.org/jira/browse/JBESB-2720?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2720.
-------------------------------
Resolution: Done
I tried out two different solutions for this, both successful and both with pros/cons.
The first was an implicit initialisation of the proxy, the second an explicit
initialisation.
In the end I decided on the explicit initialisation because it does not rely on a
side-effect (which may change) and, although it introduces an explicit dependency on
hibernate, this is unlikely to change in this jBPM stream.
Updated in revision 27739.
Force initialisation of hibernate job proxies
---------------------------------------------
Key: JBESB-2720
URL:
https://jira.jboss.org/jira/browse/JBESB-2720
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4 CP2
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.4 CP3
If no accesses are made to the job proxy before saving then the attempt to save will fail
with the following hibernate exception.
org.hibernate.PersistentObjectException: uninitialized proxy passed to save()
We need to access part of the job instance before saving in order to force the proxy to
be initialised.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira