Expand the WorkspaceRunner to run old-school (*.fme) mapping files

Hi,

When a Workbench workspace (*.fmw) is run, it's converted into a mapping file (*.fme) on-the-fly to be run by fme.exe.

I'm using "fme" files for production (called via a BAT file), while the Workbench workspaces are for testing and debugging. This is my "best practice".

But if I have one workspace that runs another, I cannot run the mapping file itself, only the Workbench workspace.

I think it would be a huge enhancement, if the WorkspaceRunner could activate a mapping file (*.fme) directly, removing the need for the on-the-fly conversion. A win-win wrt. performance too.

Cheers

Lars I.