Hide Forgot
Date of First Response: 2008-06-11 08:51:26 project_key: SOA The reconfigure macro moves files to {file}.orig, and then moves them instead of copying them - which destroys the original file. If the second move in the sequence were a copy instead of a move, it would be possible to rerun the schema script. I think the intention was to preserve the original file - the subsequent copies don't overwrite the .orig files. <macrodef name="reconfigure"> <attribute name="file"/> <attribute name="old"/> <attribute name="new"/> <sequential> <move file="@{file}" tofile="@{file}.orig"/> <move file="@{file}.orig" tofile="@{file}"> <filterchain> <replacestring from="@{old}" to="@{new}"/> </filterchain> </move> </sequential> </macrodef>
Tom - isn't this the same as: SOA-512
Tom - isn't this a duplicate of SOA-512?
I don't believe so. SOA-512 suggests that it's possible to change database configuration by removing files - this bug says that we destroy the original files so it will be impossible to accurately switch the database a second time. The original files will no longer be there to use as replacement/change templates.
Link: Added: This issue related SOA-695
Link: Added: This issue duplicates SOA-853
Verified in IR5