Community
Participate
Working Groups
When a user tries to generate a BIRT report using TPTP 4.4.1 and JDK 1.4 an exception is thrown. The report complains about a unsupported d protocol. The reason is that the report is trying to open an xml file on the D drive. This protocol is used when desigining the report and should not be used during runtime. What happens is that BIRT report engine tries to first open an XML stream in memory. If this fails it tries to open a default file on the d drive. From the BIRT download page only BIRT 2.1.x is able to work JDK 1.4. BIRT 2.1.x requires GEF 3.2, EMF 2.2 and eclipse 3.2. TPTP 4.4.1 can work with JDK 1.4 when using EMF 2.2.4 and eclipse 3.3.1. Note that there's some decrepencies between EMF versions and Eclipse versions. I fear that this may cause some conflicts when trying to run BIRT 2.1.x and TPTP 4.4.1. Resulting in generating blank reports. On another note I was able to generate reports with BIRT 2.1.x and TPTP 4.3.1 since the dependencies for TPTP 4.3.1 and BIRT 2.1.x are the same.
According to the BIRT download site (http://www.eclipse.org/birt/phoenix/build/#introduction), using BIRT 2.1.3 with the following depednancies is supported: Eclipse 3.1.3 GMF 3.1.3 EMF 2.2 JRE 1.4.2 Sheldon is investigating the root cause the of this problem.
Joe is working today on isolating the problem to either our BIRT report generators or BIRT.
I was able to get the reports working with Sun's JDK 1.4 If I compile org.eclipse.tptp.platform.report.birt and replace the org.eclipse.tptp.platform.report.birt_XXX.jar with my new compiled version the reports get generated. I used the following jdk to compile the org.eclipse.tptp.platform.report.birt plugin. Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06) Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode) I was told that TPTP is compiled with an IBM jdk. I'm not sure why this is causing a problem. I'm wondering if I use IBM's JDK 1.4 will work? I have to try this.
(In reply to comment #2) > Joe is working today on isolating the problem to either our BIRT report > generators or BIRT. > Correction, Sheldon.
(In reply to comment #3) I figured out the reason this is happening. TPTP 4.4.1 is compiled with BIRT 2.2. As a result the org.eclipse.birt.report.data.oda.xml.Constants.APPCONTEXT_INPUTSTREAM BIRT 2.2 value is inlined in the TPTP 4.4.1 class. Now, if I use TPTP 4.4.1 with BIRT 2.1.x the reports break because BIRT 2.1.x is expecting a different constant value. I opened BIRT Bug #202947 to resolve this problem.
The work around is to compile the TPTP 4.4.1 code base using BIRT 2.1.3 as suggested by bug 202947
Resolved since dependent defect (202947) has been fixed. Sheldon, can you: 1) Confirm 202947. 2) If resolved, have the 4.4.1 builds use this BIRT driver. 3) Update the hours worked on triaging this defect. Thanks Sheldon for your help!
Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
