OutputProcessXMLParameter pre-initialization used even if disabled.
Mantis Issue 1103, reported by salbert, assigned to gpasero, created: 2015-11-05
Pre-initialized output process XML parameter content is taken into account even if parameter is not enabled.
After the OTB-application has run, an exception message is popped informing that content has wrong filename extension because '.xml' extension is missing.
I'll remove the pre-initialization of output process XML parameter.
1446737800 - salbertThere may be a problem in otb::Wrapper::OutputProcessXMLParameter::SetFileName().
1446742960 - salbertRemoved pre-init of output process XML parameter in Monteverdi 3.
1446832414 - gpaseroThe problem is that, when you call otb::Wrapper::OutputProcessXMLParameter::SetFileName(), it will set the parameter to "Enabled".
1449567373 - salbertRemoved default initialization in Monteverdi3 (https://git.orfeo-toolbox.org/monteverdi2.git/commit/b82a1e2795e133b40ca7206f8d6f2be9cecb4fd1)