There must have a way to define a parameter which is a qualified name, as XSLT parameters are QNames.
More, parameter names are resolved against other parameters definitions.
I can not imagine a XSLT or a Java Step where the parameter name is not known at compilation time ; so, parameter names shouldn't go through ConfigUtil.resolveEscapes().
There must have a way to define a parameter which is a qualified name, as XSLT parameters are QNames. More, parameter names are resolved against other parameters definitions. I can not imagine a XSLT or a Java Step where the parameter name is not known at compilation time ; so, parameter names shouldn't go through
ConfigUtil.resolveEscapes()
.Change the
by