Hi Stian, > As for log4j.properties - remember to always update both > lib/log4j.properties and conf/log4j.properties. The first one will > normally be used, but the second one would be loaded by legacy Taverna > 1 code when opening Taverna 1 workflows or possibly when opening with > 'Any workflow type' filter selected (which also tries using Taverna 1 > code).
Thanks. It looks like this was the trick. I think the changes i was doing were not recognised by taverna but now i copied your example log file to under my taverna lib directory and now able to see helpful messages logged. Regards, Mahmut ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
