Hi Anthony, On 4/7/06, Anthony Bigbee <[EMAIL PROTECTED]> wrote: > Hi, > > Several questions and some bug reporting on 1.7.0pre0. > > Engine > ---------- > Should a running engine pick automatically pick up on changes to a > process definition (such as changes to etc/engine/cron.xml) if it is defined > as a <service> in etc/engine/engine-configuration.xml? Is a restart > required because I simply change the message string in cron and I'm not > seeing that reflected in history.log without engine restart.
Strange, I thought I had it working. Could you please fill a bug report for it ? http://sourceforge.net/tracker/?group_id=54621&atid=474244 > Logging > ----------- > 1. In a previous message, John Mettraux said that > 'The HistoryService has its parameters in > etc/engine/engine-configuration.xml, it's not following log4j > directives, but takes some inspiration from them.' > > While I see a service entry for "history", I don't see any parameters for > logging granularity. How is granularity specified? http://www.openwfe.org/docbook/build/apas02.html#id2529452 I think I implemented it for SqlHistory but completely forgot to 'port' it to TextHistory. This would deserve a feature request : https://sourceforge.net/tracker/?group_id=54621&atid=474247 > 2. I cannot find any mechanism for controlling pyya-apre logging > verbosity. All I can see is that standard error and standard output are > redirected to $LOG in bin/pyya-apre.sh (which for some reason, logging is > still going to the console). The output has entries like INFO, so > presumably this is controllable. Whoah, it's been so long since I received the last question about pyya-apre. Controlling log verbosity hasn't yet been implemented. It could be done though by modifying openwfe/applic/__init__.py > 3. My first attempt to control granularity of apre.log doesn't seem to > have worked. I'm still getting DEBUG and INFO for [main]. > I tried this: > <category name="org.apache.axis"> > <priority value="ERROR"> > <appender-ref ref="axis-file" /> > </category> > > <category name="openwfe.org"> > <priority value="ERROR"> > <appender-ref ref="file" /> > </category> > > <root> > <priority value="ERROR" /> > <appender-ref ref="file" /> > </root> > > Any suggestions? You could try to set the level at 'WARN'. > It would be nice if the manual/book had an explicit section on logging that > covers all logging. Feature request... > pyya-apre > -------------- > I found that the following pyya-apre files probably should be modified. > > openwfe/engine/participant.py > DEFAULT_PMAP_FILE = 'etc/engine/participant-map.xml' > > bin/pyya-apre.sh (ditto for pyya-apre.bat) > PYTHONPATH=$PYTHONPATH:$ETC/lib > > pyya-apre-scripts/ToPdfAgent.py (ditto for EmailNotificationAgent.py) > from openwfe.apre import Agent Could you generate the appropriate patches and upload them ? http://sourceforge.net/tracker/?group_id=54621&atid=474246 Thanks for reporting and thanks in advance for the project tracking items. Have a nice week-end, -- John Mettraux -///- http://jmettraux.openwfe.org ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ OpenWFE - Open source WorkFlow Engine OpenWFE-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openwfe-users
