It's all about the answers!

Ask a question

Unable to work with BIRT after upgrade to RTC 3.0


Tal Rabinovitch (4721615) | asked Apr 11 '11, 9:59 a.m.
Hi,
Our RTC server and clients were just upgraded to 3.0. Since then I can't work with birt (the perspective is not loaded properly).
I tried upgrading the needed components to the following versions (after reading about it in the forum), but still no success:
birt-report-framework-sdk-2_5_2
dtp_1.7.2
emf-xsd-SDK-2.5.0
wtp-sdk-R-3.1.2-20100211202452

Can someone give the exact needed components (with their versions) which are needed in order to run BIRT on RTC 3.0 ?

Thanks,
Tal

2 answers



permanent link
Steven Hyde (10692) | answered Apr 12 '11, 4:11 p.m.
JAZZ DEVELOPER
Hi,
Our RTC server and clients were just upgraded to 3.0. Since then I can't work with birt (the perspective is not loaded properly).
I tried upgrading the needed components to the following versions (after reading about it in the forum), but still no success:
birt-report-framework-sdk-2_5_2
dtp_1.7.2
emf-xsd-SDK-2.5.0
wtp-sdk-R-3.1.2-20100211202452

Can someone give the exact needed components (with their versions) which are needed in order to run BIRT on RTC 3.0 ?

Thanks,
Tal


Yes me too. I followed all the directions in the wiki but still I get an error (a warning actually) that "The opening design file is not a valid design file or the file does not exist"
Then when I hit OK on that I get the 'XML Source' tab displayed but clicking on any other tab throws an error;
"Error in XML Source Page must be corrected before other pages can be used."
This is creating a new blank report.

This is the XML that is shown;
<xml>
<report>
<property>Eclipse BIRT Designer Version 2.5.2.v20100208 Build <2.5.2.v20100210-0630></property>
<property>in</property>
<property>/templates/blank_report.gif</property>
<property>ltr</property>
<property>96</property>
<styles>
<style>
<property>sans-serif</property>
<property>10pt</property>
</style>
<style>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
</style>
<style>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
<property>#CCCCCC</property>
<property>solid</property>
<property>1pt</property>
</style>
</styles>
<page>
<simple>
<page>
<text>
<property>html</property>
<text><!]></text>
</text>
</page>
</simple>
</page>
</report>

permanent link
Steven Hyde (10692) | answered Apr 12 '11, 4:24 p.m.
JAZZ DEVELOPER
I have found it has something to do with using my existing workspace.
If I create a clean project, I don't see the issue and the XML is identical.
I guess I'll create a new workspace.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.