Currently I'm figuring out whether the BIRT is a gift from heaven, or a one way trip to hell. At the moment, I think the roadsigns lead me into hell, instead of the start of the rainbow.
My first pet peeves:
- the dataset editor is a modal dialog. This inhibits looking at your mappings in your Java classes, hibernate mapping files, etc. Why couldn't this be just an editor window in the usual Eclipse style of editing?
- dragging columns in the dataset editor is no help at all. It prefixes the schema name, table name and column name on the place where the cursor is in the editor window. It doesn't add a from clause, nor does it have any intelligence on foreign key relationships.
- the scripted dataprovider/dataset is a drag in working with Java, when you have a coding problem, it only shows up when previewing, and it doesn't provide you with a sensible error message: "The value of the property 'keyExpr' is required". I tried looking for this property in the xml definition of a valid report, but couldn't find one. How am I supposed to know where and how to set this?
- you can only see the report working when you copy your classes into the report viewer plugin's web directory. Why isn't it possible to have it use the classpath of your current project, giving it the full capabilities of hotswap?
- In order to have the previewer pick up changes in my Java code, I had to restart my workspace every time
- It is very easy to have it take 100% of CPU and make your machine come down to a crawl, making you kill the Eclipse process. This problem did go away with an update of the EMF/GEF feature through the update manager.
As you can see, I am not enthousiastic about the BIRT offering. It sure doesn't feel like a 2.0 release, more like a 0.1 development snapshot.