Closed N-Bojovic closed 4 months ago
Are you sure it is Jaspersoft Studio 7 that you are using? I tried it myself and it works.
Can you attach here your JRTX file?
Thanks, Teodor
I'm using JS7.
This file format is not supported to be attached on this platform but here is the content of it:
<?xml version="1.0"?>
<!DOCTYPE jasperTemplate
PUBLIC "-//JasperReports//DTD Template//EN"
"http://jasperreports.sourceforge.net/dtds/jaspertemplate.dtd">
<jasperTemplate>
<style name="SuperFont" fontName="Arial" isStrikeThrough="false" pdfFontName="Helvetica" />
<style name="Font6" style="SuperFont" fontSize="6"/>
<style name="Font8" style="SuperFont" fontSize="8"/>
<style name="Font9" style="SuperFont" fontSize="9"/>
<style name="Font10" isDefault="true" style="SuperFont" fontSize="10"/>
<style name="Font12" style="SuperFont" fontSize="12"/>
<style name="Font14" style="SuperFont" fontSize="14"/>
<style name="Font16" style="SuperFont" fontSize="16"/>
<style name="Font20" style="SuperFont" fontSize="20"/>
<style name="BoldFont6" style="Font6" isBold="true" pdfFontName="Helvetica-Bold"/>
<style name="BoldFont8" style="Font8" isBold="true" pdfFontName="Helvetica-Bold"/>
<style name="BoldFont9" style="Font9" isBold="true" pdfFontName="Helvetica-Bold"/>
<style name="BoldFont10" style="Font10" isBold="true" pdfFontName="Helvetica-Bold"/>
<style name="BoldFont12" style="Font12" isBold="true" pdfFontName="Helvetica-Bold"/>
<style name="BoldFont14" style="Font14" isBold="true" pdfFontName="Helvetica-Bold"/>
<style name="BoldFont16" style="Font16" isBold="true" pdfFontName="Helvetica-Bold"/>
</jasperTemplate>
It seems you are affected by the same JSS7 bug and should try the same workaround as explained here: https://github.com/TIBCOSoftware/jasperreports/issues/453
Thank you, Teodor
I already did that, but the problem occurs when I open file that I want to update through Jasper Studio 7, not during update. So at the end what I did is removed "is" prefix and then open file in JS7, when it was correctly loaded I could execute conversion. My question is now if those changes I did on properties (e.g. isBold -> bold) will have any impact in my reports?
If you are saying that your existing JRTX files still point to a DTD, it means they are very old. Prior to JasperReports version 6.3.0 from 2016, when we deprecated DTD and replaced it with XSD. If that's the case, then you need to use Jaspersoft Studio 6 or older to upgrade them from DTD to XSD and then use JSS7 to migrate to the new syntax. So you do it in two steps. In version 7 we decided to no longer read DTD based files as they are very old.
I hope this helps. Teodor
Indeed, this is really old jrtx file. Do you have any tip how to do this from JR6 (DTD to XSD)?
Just open the file in designer/editor, simulate a fake change and save it back.
I hope this helps. Teodor
For some reason it's not working for this .jrtx file. On the other hand I had few .jrxml templates based on DTD and when I open them in JR6 and made dummy change it did remove DTD section. Either way, I have fixed .jrtx manually, so I think this thread can be closed.
Thanks teodord!
Hi,
I wanted to update my ReportStyleTemplate.jrtx file to a new style from within Jasperstudio 7.0, but when I open this file it throws this exception (see bellow). When I change all attributes that start with 'is' (isStrikeThrough -> strikeThrough; isDefault -> default; isBold -> bold) I don't have this error anymore and file can be converted to a new style. Is it safe to change those properties to be without prefix 'is', or reason for this is something else and I should fix this problem differently?