Page 1 of 1
Batch XSLT2.0-Conversion
Posted: Fri Sep 09, 2011 2:11 pm
by patrick
Hi,
I'm doing a project-wide batch transformation.
Actually, the output of xsl:message is shown in the message tab only for the current xsl file, so if the transformation is over, I can get the messages only from the last file.
How can I store all the xsl:message-output into one logfile?
Thanks,
Patrick
Re: Batch XSLT2.0-Conversion
Posted: Fri Sep 09, 2011 8:41 pm
by sorin_ristache
Hello,
You are right, each XSLT transformation resets the Messages view instead of appending the messages issued by xsl:message elements to the messages of the previous transformations. We will fix this in a future version so that the messages of the previous transformations are preserved in the Messages view.
I thought I could give you a workaround for the current Oxygen version by suggesting to output the messages also to a separate file using the xsl:result-document element, in addition to outputting them with the xsl:message one. Unfortunately it does not work because the entire content of a file created by the xsl:result-document element must be output in the same xsl:result-document element which you cannot do if you have xsl:message elements in different xsl:template elements of the same XSLT stylesheet.
Regards,
Sorin
Re: Batch XSLT2.0-Conversion
Posted: Mon Apr 06, 2015 3:34 pm
by Costin
Hello,
I just wanted to let you know that this problem has been resolved in the latest version (v16.1) of Oxygen.
If you have a license compatible with version 16 of oXygen XML, you can download the latest maintenance build of v16.1, 2015012213 (released on January 26th) from our web site:
http://www.oxygenxml.com/download.html
The complete what's new list is available here:
http://www.oxygenxml.com/whatisnew16.1.html
To upgrade:
- For Windows and Linux you can install the new build in the same folder as the previous installation, it will automatically upgrade it.
Before you upgrade, if you have added files or made changes to any of the files from the Oxygen installation folder(especially the frameworks folder), you may want to create a backup of them because they will be overwritten during the upgrade procedure. Custom frameworks will be preserved but we recommend backing them up anyway, just to be safe.
- For Mac OS X you will have to either move the old folder from Applications to a different location and put the new version of Oxygen in its place, or install in a different folder. You can then copy any files you may have changed from the old folder (if any) to the new folder.
The Oxygen preferences will be preserved since they are located elsewhere (user home folder) and they will be imported at the first run of oXygen.
Let us know if you encounter further problems with the new version.
Regards,
Costin