A custom Java transformer chained after a core XSL transformer in an IFS Connect routing address subtly corrupts file content in a way that's hard to pin down, even though the transformer's logic looks correct and works in isolation.

All FAQ questions / Integrations and APIs

Answer

If a custom Java transformer behaves correctly in your IDE/tests but produces subtly different output once deployed, check for a Java version mismatch between your development environment and the actual runtime the application uses (for example, developing against Java 17 while the platform runs Java 11) — this can silently change default behaviors like line-ending characters. To diagnose it, Base64-encode both the expected and actual output and compare the encoded patterns for newline characters (\n encodes differently than \r\n); a byte-size difference between otherwise-identical content is a strong hint that this is exactly what's happening, and explicitly normalizing the line endings your transformer produces resolves it.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions