I am using PDFBox jar to print the pdf generated from my BIRT module.
BIRT version is 4.3.1 which i am planning to upgrade.
I just wanted to know that BIRT uses PDFBox or IText internally to generate the PDF.
If i use PDFBox with BIRT 4.3.1 do i have to worry that it might cause issues with BIRT PDF generation if BIRT is using some other version of PDFBox jar internally.
I am not sure but I've heard that birt uses iText to generate pdf. Just test it. It's the saves way to get this sure if it really works.
Related
We are upgrading from iText 2.1.7 to the iText 7.1.13 latest version. we are not using maven. Its a existing project so we cant change it to maven. Just directly adding the jar. For the iText 2.1.7 we have iText-2.1.7 jar, but now I can't seem to find the main iText-7.1.13 jar. where can I get iText jar.
The zip files here provide the supporting jar but does not contain - iText jar. https://github.com/itext/itext7/releases/tag/7.1.13
For iText 7 there is not one single jar, it is split up in several modules. You need all the jars in the ...-only-jars.zip on the page your provided. Ok, maybe not all the jars, if you don't use certain features, but at least io, kernel, layout and maybe other modules too, depending on which features you need. For example if you don't use barcodes then you don't need the barcodes jar.
Also, iText 7 is a complete rewrite, and the API is not backwards compatible. Which means that you may need to rewrite parts of your code.
I was using BIRT together with java 1.6 but recently have updated java to the latest version which is a prerequistie for other applications. Since then BIRT is not working.
I was using BIRT 4.4.0.v201405191524.
Is there any possibilty to work BIRT with the java 1.8 version?
BIRT has some dependencies which are given here.
They have specifically mentioned only Java 1.6 JDK/JRE as a pre-requisite but not higher version of JDK/JRE.
The BIRT engine 4.5 itself is still compiled with a java 6 compliance but many eclipse libraries require java 1.7.
I'm using BIRT 4.3.2 v20140211-1400 with java 1.8.
I'm using jre 1.8.20 and compiler version 1.8.
We recently upgraded our Dev environments to use BIRT 4.6.0 v20160607-2122 with Java 8_121, using Eclipse Neon 4.6.2
All is well, BIRT works great, with one minor issue: on the Edit Chart dialog's Select Data tab, the Summation button for the Value Series / Slice Size Definition is always disabled.
I'm new(ish) to Java/Netbeans/ControlsFX. I know about Javadoc and would like NetBeans to show me javadoc for ControlsFX. I see the online version of the docs for ControlsFX but that defeats (at least part of) the purpose of using an IDE? I know how to add the doc zip file in NetBeans but I don't see the doc file for ControlsFX.
Am I missing something?
Found this lately. ControlFx java doc. You can manipulate the version number at the end of the url to get to page of any other version of the doc if it is in existence. Download the jar version on that page to use it locally controlsfx-version-javadoc.jar. Then you can add the jar in your netbeans Javafx project.
I have a XSD file with assertion tags. I have read that Xerces supports a XML Schema 1.1 draft with these tags.
How can I use an actual Xerces version, instead of the standard Java implementation, in my maven build.
An old way to use the Xerces version was adding those parameters. I do not know if it could still work.
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParser=org.apache.xerces.jaxp.SAXParserImpl
We have a project where we're using Spring-js. With it comes Spring-dojo and the full dojo package. But in the current version of Spring-js (2.0.9), it's using dojo 1.3. Is there a way to upgrade manually to dojo 1.4? Or even a new Spring-js.jar-file that can be donwloaded that uses dojo 1.4?
Yes. If you are using the ResourceServlet, you can simply drop the new version of Dojo in the top-level directory of your WAR structure. The ResourceServlet always looks there before it looks on the classpath, thus resources in top-level of the WAR take precedence. I would suggest using a full uncompressed source distro of Dojo during development, and then doing a custom build that is tailored to your usage patterns for production.
Beware that we've occasionally seen some minor incompatibilities when upgrading Dojo versions, so be on the lookout for that and report any issues in the Web Flow Jira.
I suspect we'll be upgrading to Dojo 1.4 in the official distribution for the upcoming Spring Web Flow 2.1 release.
Btw., spring webflow 2.0.9 uses dojo 1.2.4 not 1.3 as the release notes tell