Replies: 9 comments 5 replies
|
I think you can lookup the answers to these questions yourself here: https://www.eclipse.org/projects/ |
|
Maybe you can give me a hint how to find the answers there, especially for the most important question, the 3rd one? I only find the git repo for the project - but this was not a question. |
|
The project page is the central place for every project. From there you can see how many committers there are (2), that the project source is not on Github and that the project is minimally maintained (a couple of commits to get the build working). I don't think we can include datatools since many projects might rely on them. The parsing issue you present looks like sloppy programming. I don't think embedding datatools will fix that. I agree that we should be concerned by the fact that datatools is not very active. |
|
Embedding will not fix the problem, of course. Alternatively, I can image about an alternative XML Data source parsing mode (maybe we should introduce a checkbox on the data source) which will not use datatools at all, e.g. by using DOM and reading everything (one-time) into memory. |
|
It actually looks like there will be a change of management in datatools soon. https://www.eclipse.org/lists/dtp-dev/2021/Nov/index.html The project seems to have both gerrit and ci enabled, with some 230 unit tests, so if you file bugs and push PRs you might have a good chance to get them reviewed and applied. |
|
Thanks for the update. Is there a way to import a datatools working copy into the BIRT development environment in order to locally modify datatools but to be able to test it with BIRT as well? |
|
@patric-r I think you can try to import any bundle from target platform to your BIRT workspace via |
|
Just try to add some back ground here. Actuated was working with DTP team together by providing some extensible framework for BIRT to leverage. If @patric-r you'd like to fix anything but is worry about if DTP is going to adopt it, you could try to implement your own data source. This will be only depending on a small piece of DTP which means you can contribute your code either in your won github repo, or as a sub project here in BIRT. You may want to take a look at org.eclipse.birt.data.oda.mongodb as an example. |




Uh oh!
There was an error while loading. Please reload this page.
BIRT uses many classes from the datatools project, e.g. for the XML data sources (e.g. org.eclipse.datatools.enablement.oda.xml).
We're facing many issues with XML data sources (mainly performance issues)
E.g. for each data set access from a XML data source, the xml will be parsed again and again (using SAX).
For some input xmls with only a few hundred kilobytes, PDF rendering takes more than 30 seconds and >= 90% of the time is spent in the datatools project and profilers show that same xml is parsed for more than 200 times in our use case/report.
Questions:
Wouldn't it make sense to integrate the datatools project into BIRT as well?
All reactions