All,
A common pattern I've been using within NeuronESB is transforming an XML message into a CSV file, using an XSLT Step within a Process. I typically craft the XSLT as an XSLT transformation within the 'Repository', and then import the XSLT from the Repository into the XSLT Process Step.
For some CSV files, I have been including a HTML character for carriage return:
Including the special character within the XSLT in the Repository works fine, and the output from the 'Test' button creates the CSV in the format I expect.
However, when I import the XSLT saved in the Repository into an XSLT Process Step, the carriage return is removed from the Transform editor (in the Process), and the CSV output from the Process does not include the carriage return.
Within the XSLT Transform editor (in the Process), I see the following:
Is there a more advisable method of creating carriage returns within an XSLT transformation?
Is there an alternative to having to re-edit an XSLT transformation in a Process Step to re-add carriage returns that already exist within an XSLT Transformation in the Repository?
Thanks!
Tags:
can you send us a project that includes the documents and steps to replicate?
Additionally, I have tried using the 'Enter' key on my keyboard to code a carriage return within the XSLT Transformation in the Repository. The 'Enter' key also adds a carriage return into the CSV output.
However, when I import an XSLT into a Process Step that has an 'Enter' key in the XSLT Transformation in the Repository, that character is also removed from the XSLT editor in the Process Step.
Please try it ‘&#13' instead of '
'
‘&#13' does not seem to work in the Repository tester, nor during the Process Step.
In the Repository editor, the output is literally 
 within the Output.
Within the Process Step, the only output is the value '13' (with no other output).
Attached a project, as well as documentation to replicate.
Manoj,
Can you provide the steps you used to verify that this works?
When I used <xsl:text><![CDATA[ ]]></xsl:text> within the XSL Transformation tester, the output nearly contained the literal, and displays as: &#13;
When I used <xsl:text><![CDATA[ ]]></xsl:text> within the XSL Transform Process Step, the Trace output is simply 13;
Am I misunderstanding where this tag can be used?
Garrett,
I figured later it is not working with CDATA as well, so I have taken out that reply, What Neuron build you are using? we actually have to give you new build with this fix...
Thanks,
Manoj
Manoj,
We are currently using 3.5.4.840.
Thanks,
Garrett
Hi Garret,
Please use the following xslt document, this should work :)
Hi Manoj,
Thank you for the attached XSLT. I did use the 'nl' variable construct, and that did resolve the issues that I was seeing in my original post.
Thank you,
Garrett
Can a document be provided that shows how it was verified that this issue was resolved in builds 981 and subsequently 982?
I've upgraded to 982, and do not see that the original cases have been resolved.
Hi Garret,
Can you provide me your email address?
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin. Powered by