Locking transform inputfiles
Posted: Wed Mar 10, 2004 5:04 pm
Hi,
When using transformation scenario, the input files get blocked. I try to create a step process with a lot of XSLT sheets working like this:
input xml -> XSLT step1 -> output=input xml -> XSLT step 2 -> result xml
When this is configured, and I run step 1, the output file cannot be written because its locked by step2. (It should be possible to delete the middle xml file so that it has to be generated by step1, but when that file exists, its locked by step2 and thus not deletable)
I wood like the xml input/output files not to be locked until the file is actually read, and after the reading it should be unlocked directly.
Is there any reason why the files are locked?
Kind Regards,
Jan
When using transformation scenario, the input files get blocked. I try to create a step process with a lot of XSLT sheets working like this:
input xml -> XSLT step1 -> output=input xml -> XSLT step 2 -> result xml
When this is configured, and I run step 1, the output file cannot be written because its locked by step2. (It should be possible to delete the middle xml file so that it has to be generated by step1, but when that file exists, its locked by step2 and thus not deletable)
I wood like the xml input/output files not to be locked until the file is actually read, and after the reading it should be unlocked directly.
Is there any reason why the files are locked?
Kind Regards,
Jan