This content has been marked as final.
Show 4 replies
-
1. Re: setup for jbpm logging
wrschneider99 Jun 6, 2006 12:02 PM (in response to wrschneider99)"wrschneider99" wrote:
I have the <service name='logging' factory='org.jbpm.logging.db.DbLoggingServiceFactory' /> set up in jbpm.cfg.xml.
whoops, forgot code tags. I have this in my jbpm.cfg.xml:<service name='logging' factory='org.jbpm.logging.db.DbLoggingServiceFactory' />
-
2. Re: setup for jbpm logging
wrschneider99 Jun 6, 2006 2:50 PM (in response to wrschneider99)I seem to have answered my own question.
If I call context.save(processInstance) explicitly, the logs get saved.
Otherwise, everything else seems to work but the logs don't get written.
Wonder why this is? -
3. Re: setup for jbpm logging
kukeltje Jun 7, 2006 3:30 AM (in response to wrschneider99)this behaviour is as designed. If you look at alll the examples how to uyse the api, you'll see an explicit 'save'
-
4. Re: setup for jbpm logging
wrschneider99 Jun 7, 2006 8:13 AM (in response to wrschneider99)"kukeltje" wrote:
this behaviour is as designed. If you look at alll the examples how to uyse the api, you'll see an explicit 'save'
So I wonder why everything else worked without the save call?
Perhaps it's because I'm managing my own transactions, and the commit forced a flush for all the modified Token/ProcessInstance objects--but the ProcessLog objects were newly-created and never associated with a Session at all so they didn't get saved.