version 3.2.17 is invalid for it is greater than the latest supported one?

Hi,

Would appreciate any ideas on this..

I tried to modify a report that originally designed in BIRT 3.2.0. Once the .rptdesign file is updated and saved, the report version is updated to "3.2.17" (The latest BIRT 3.2.1 plugin is installed).

I've also updated the dependencies and all latest 3.2.1 BIRT jars are on the classpath.

Once the project is compiled and redeployed, the report throws following errors:

Caused by: org.eclipse.birt.report.model.parser.DesignParserException: The report file of version "3.2.17" is invalid for it is greater than the latest supported one.
at org.eclipse.birt.report.model.parser.ModuleState.parseAttrs(ModuleState.java:110)
at org.eclipse.birt.report.model.parser.ModuleParserHandler.startElement(ModuleParserHandler.java:198)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:454)
at org.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamespaceBinder.java:571)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:756)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:752)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:942)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1520)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.eclipse.birt.report.model.parser.ModuleReader.readModule(ModuleReader.java:95)
... 31 more

Any ideas?

Find more posts tagged with

Comments

Virgil Dodson

Hi zaus,

BIRT 2.3.1 should show 3.2.17 version in the XML source...
and BIRT 2.3.0 should show 3.2.16.

If you have replaced the JARs with BIRT 2.3.1 jars then everything should work correctly. If you modify the XML source and change the version to 3.2.16 and it works correctly, then I would doublecheck that the BIRT 2.3.0 runtime jars are not sneaking into the classpath somehow.

CoolCat

hi vdodson,

And what can we do in this case:

Caused by: org.eclipse.birt.report.model.parser.DesignParserException: The report file of version "3.2.17" is not supported.
at org.eclipse.birt.report.model.parser.ModuleState.parseAttrs(ModuleState.java:109)
at org.eclipse.birt.report.model.parser.ModuleParserHandler.startElement(ModuleParserHandler.java:190)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:798)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:878)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:1157)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1794)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.eclipse.birt.report.model.parser.ModuleReader.readModule(ModuleReader.java:95)
... 26 more

Virgil Dodson

Hi CoolCat, if you are also seeing this message, then can you tell me how you are deploying your reports? 
 
If you are using the BIRT Engine, then make sure your application (and app server lib, if appropriate) are updated with the latest JARs from the BIRT 2.3.1 runtime download. 
 
If you are using the BIRT Web Viewer, then redeploy the newest birt.war from the BIRT 2.3.1 runtime download. 
 
If you are using the Actuate Interactive Viewer or Actuate iServer, then you can download the Actuate 10 beta from <a class='bbc_url' href='http://www.birt-exchange.com/wiki/Actuate_10/'>Actuate 10 - BIRT Wiki - BIRT Exchange</a> which supports the BIRT 2.3 files.

CoolCat

I've this message when I use debug for my '.java' program (I'm sory, I'm french, I don't have a good english and I don't know if you undertand me very well...).
I'm trying to create a program which can build a report using ".rptdesign" file, ".jar" of my program and a Visual Basic program. It's hard for me to explain why I'm doing this in english, but I can only say that It's for making my ".rptdesing" communicate whith AXIANT (I don't know if u understand...)

Virgil Dodson

It sounds like you are using the BIRT Engine APIs to generate reports from your rptdesign files. In that case, make sure you have download both the BIRT 2.3.1 Designer... AND the BIRT 2.3.1 Runtime which contains all the BIRT JARs needed. Using these together and you should not see this message.

amul

<blockquote class='ipsBlockquote' data-author="vdodson">Hi zaus, 
 
BIRT 2.3.1 should show 3.2.17 version in the XML source... 
and BIRT 2.3.0 should show 3.2.16. 
 
If you have replaced the JARs with BIRT 2.3.1 jars then everything should work correctly. If you modify the XML source and change the version to 3.2.16 and it works correctly, then I would doublecheck that the BIRT 2.3.0 runtime jars are not sneaking into the classpath somehow.</blockquote>
 
I just did as above and it worked out perfectly. 
thanks alot 
 
regards 
amul