id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
112	Status file location error on long processes	espen		"When a program specified as the ""serviceProvider"" in the service configuration is located in another folder than the current working directory, the filename of the status file will be wrong. It looks like the generated status filename will be created on the form: {{{$main_conf['main']['tmpPath'] + serviceProvider +'_' + sid +'.xml'}}}. 

This will cause problems because the folder do not exist. 

Ex:
{{{ 
[serviceName]
serviceProvider = c:/zoo/php/script/foo.php
}}}

The service folder is:
{{{
$main_conf['main']['tmpPath'] = c:/zoo/wps/status
}}}

The status file will be something like:
{{{
c:/zoo/wps/status/c:/zoo/php/script/foo.php_XXXX.xml
}}}

To use the ""service name"" instead of serviceProvider as status file name will probably solve this issue. 

"	defect	new	major		Development platform