Bill, Ronald,
FWIW... for ordinary log4j logging, just include a log4j.xml with an ordinary
file-based appender, e.g., org.apache.log4j.RollingFileAppender, or similar.
I don't understand exactly what role DbLoggingService et al play. I wanted
ordinary logging, realized that log4j wouldn't
Logging: http://docs.jboss.com/jbpm/v3/userguide/logging.html
It could/will be used to implement a kind of undo/rollback mechanism.
Logging related jira issues:
http://jira.jboss.com/jira/browse/JBPM-166
View the original post :
no, sorry, not by default
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4049003#4049003
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4049003
___
jboss-user mailing list
thanks Ronald,
but, why not by default? does this mean that there is a customized way to do
this ?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4049006#4049006
Reply to the post :
lots of things are customizable in jBPM. Logging is (afaik) one of them (look
at the 'services' configuration), but I have no clue on how to do that or if
there are still any hidden issues (it has never been done)
View the original post :
I've looked at services configuration in jBPM doc.
By default,jBPM provides an implementation of Logging services through 2
classes:
DbLoggingServiceFactory which implements ServiceFactory
| DbLoggingService which implements LoggingService
|
| I guess that for my problem, I should provide
Hey, I never said it was going to be easy ;-), and why are you surprised you
are the first one to need this? Can you tell why you want to replace db with
file?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4049018#4049018
Reply to the post :
I want to replace db with file for 6 reasons:
1. process definition are in an xml file,not in a database
3. I don't want to create a database with all jBPM tables (28) just for logs.
2. information which is really interesting is the result of the process,ie
OK,KO or another possible issue.
4.
1: designtime it is in the DB, deploytime it is converted to db entries
3: it is only to a small extend for logs (although it might be the biggest
amount of data)
2: ok
4: so try do disable them (has been discussed on the forum, also not easy, but
usable for more people if you contribute)
5: ok,
sorry
1: designtime it is xml, deploytime it is converted to db entries (unless you
create it each time via your own methods)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4049055#4049055
Reply to the post :
anonymous wrote : 3: it is only to a small extend for logs (although it might
be the biggest amount of data).
that's the problem!! I don't want to use a database to store process (even at
deploytime). So, if I use db logging,i must create a database just for that.
(I works on a JAVA SE
11 matches
Mail list logo
