I ran into a similar problem when using the Hypersonic database within jBoss
and my temporary solution when saving a ProcessDefinition was to catch the
exception that is generated during the commit.
As in:
jbpmSession.beginTransaction
jbpmSession.getGraphSession().saveProcessDefinition( pd )
try
{
jbpmSession.commitTransaction();
}
catch( Exception e )
{
// Ignore
}
finally
{
jbpmSession.close();
}
I found that things gets persisted correctly even though the exception is
generated. I don't like ignoring the exception but I don't know enough about
Hibernate and its configurations and I don't have a sufficient development
environment to investigate further.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915380#3915380
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915380
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
