Thanks for replying. I'm not good at gymnastics and juggling either (but it's
always good for a laugh ; ).
Could you elaborate on your view of what JBPM_LOG is for?
I don't see a point in reanalyzing every task of a process every time I want to
provide a log to my users. I know I could store th
That makes two of us. I hope you get an answer as my questions where barely
answered a year ago.
The need for actor ids in logging is fundamental to answering the three basic
questions: Who did What and When.
There's currently What happpened and When but finding Who did What requires so
much
hmmm, I'm pretty sure it was configurable in a previous version. At least,
that's what I did (setting my classname in a configuration file). I didn't have
to modify the jbpm code.
Was anything changed in the latest release?
View the original post :
http://www.jboss.com/index.html?module=bb&op=v
"bviveiros" wrote : However, I am still seeing the following warning. Any
ideas?
|
| [resource.connectionmanager.TxConnectionManager] Prepare called on a local
tx. Use of local transactions on a jta transaction with more than one branch
may result in inconsistent data in some cases of fail
I'm also trying to have a working configuration using jbpm with JTA and
encountering various problems.
My setup differs largely from yours but looking at your code, I see that you
are getting the session by creating the context and not by opening a
connection/session.
Have you had a look at thos
(by "good luck!" I mean "hope it helps!" ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923005#3923005
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923005
---
This is what the documentation has to say about turning off logging ( in
http://docs.jboss.com/jbpm/v3/userguide/logging.html) :
"For deployments where logs are not important, it suffices to get rid of the
optional LoggingDefinition in the ProcessDefinition. That will prevent
LoggingInstances f
