How I handle it: when the type object is tested, I also check if the type have been resolved (<=> a full class path exist)
But I think the type transformation should be reworked, lots of similar XSL instruction exists. They look alike but are slightly different, which cause the maintainability cost to be quite high.
All those cases should be refactored into one XSLT function (or at least be in the same file, to avoid searching in multiple places).
I should have covered all cases.
How I handle it: when the type
object
is tested, I also check if the type have been resolved (<=> a full class path exist)But I think the type transformation should be reworked, lots of similar XSL instruction exists. They look alike but are slightly different, which cause the maintainability cost to be quite high.
All those cases should be refactored into one XSLT function (or at least be in the same file, to avoid searching in multiple places).