hi,
I upgraded to Myeclipse 7.0.
I created a new report project and add a new report.
I added a data source and a data set, and enter the sql.
When i closed the dialog and reopen it and click "Query", got error "NullPoint".

So i can't change the sql any more after created it.
I can only edit the sql as the raw xml.
It should be a bug, please check it.

thanks.

zhoun,

This is infact a bug that we have on the fast-track to fix in the next patch release. We are really sorry for this one, the trick seems to be getting the query right the first time or trying to modify it directly in the report XML as a workaround -- we are really sorry this one slipped by QA.

There was another question:
The "reporting functions" in expression builder were always empty.
Another bug?

please check it, thanks.

support-rkalla wrote:

zhoun, This is infact a bug that we have on the fast-track to fix in the next patch release. We are really sorry for this one, the trick seems to be getting the query right the first time or trying to modify it directly in the report XML as a workaround -- we are really sorry this one slipped by QA.

response?

In addition to the "null pointer" bug, when I deployed I encountered the following error in Tomcat:

java.lang.NoSuchMethodError: org.eclipse.birt.report.engine.api.EngineConfig.getLogFile()Ljava/lang/String;

No such problems exists when a report is created and deployed in 7.0 M2.

has another one:
it's can not create DataSet type for Store Procedure Query,pls resolve it quick, i got emergency in BIRT development. thx in advance.

Hey all,

we recently moved from Birt 2.2 to Birt 2.3.1, everything went fine but now I got this "NullPointerException" problem when clicking on a dataSet in the MyEclipse Report Perspective. Funny thing is, everything worked perfectly when using 2.2, and now that I upgraded to 2.3.1 I seem to meet some bug fixed a long time ago (seeing the dates on this topic) oO

Does anyone have a clue? Has this bug really been fixed? Any help is welcome, thank you!
RaumsOg

@zhoun - Can you list the steps to help me reproduce this issue.

@mcnamara7 - You seem to be working with a milestone release of MyEclipse. Can you upgrade to MyEclipse 7.0 GA and test this again.

yes, i list the steps in the other topic.
http://www.myeclipseide.com/PNphpBB2-viewtopic-t-22404.html

support-nipun wrote:

@zhoun - Can you list the steps to help me reproduce this issue. @mcnamara7 - You seem to be working with a milestone release of MyEclipse. Can you upgrade to MyEclipse 7.0 GA and test this again.

The dev team is looking into this issue. They will get back to you with a response asap.

Raumsog wrote:

Hey all, we recently moved from Birt 2.2 to Birt 2.3.1, everything went fine but now I got this "NullPointerException" problem when clicking on a dataSet in the MyEclipse Report Perspective. Funny thing is, everything worked perfectly when using 2.2, and now that I upgraded to 2.3.1 I seem to meet some bug fixed a long time ago (seeing the dates on this topic) oO Does anyone have a clue? Has this bug really been fixed? Any help is welcome, thank you! RaumsOg

up (?)

support-rkalla wrote:

zhoun, This is infact a bug that we have on the fast-track to fix in the next patch release. We are really sorry for this one, the trick seems to be getting the query right the first time or trying to modify it directly in the report XML as a workaround -- we are really sorry this one slipped by QA.

What is the status of this bug fix? I am trying to build a report with parameters and this bug is preventing me from doing so. I am receiving the bug in the same manner as the original post. I create the data set, then when I go back in to add the parameter to the query... I get the java.lang.NullPointerException.

Is there a work-around for this?

OK... I am new to MyEclipseIDE... but I figured out that I could manually add the ? for each of the parameter columns.

Regardless though... this is a pretty big bug... why hasn't it been fixed yet?

This was fixed *right* after 7.0 shipped and will be in our 7.1 release at the end of this month. The workaround right now (which is sub optimal) is to edit the report XML directly to fix the query. I'm really sorry about this guys -- dev team has promised me it's fixed.

Thanks,
I think a lot of us have been waiting for this fix -- birt reports is a big selling point for me to my supervisors...