We found out that currently the velocity transformer is always executed, regardless of whether the mapping specifies the velocity transformer.
On big projects this means that a bug in this Velocity plugin (or velocity itself) breaks Wiremock mappings that do not use this transformer. Also this incurs a (small) performance penalty in very large setups.
We found out that currently the velocity transformer is always executed, regardless of whether the mapping specifies the velocity transformer.
On big projects this means that a bug in this Velocity plugin (or velocity itself) breaks Wiremock mappings that do not use this transformer. Also this incurs a (small) performance penalty in very large setups.
According to http://wiremock.org/docs/extending-wiremock/#non-global-transformations this can be adjusted by the globally flag. It would be great if this could be set to false, or that we could have a means to influence this behavior.