Eclipse Community Forums: BIRT » Eclipse debug perspective issue with required report parameters

Help

Home

Home » Archived » BIRT » Eclipse debug perspective issue with required report parameters

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse debug perspective issue with required report parameters [message #941039]

Fri, 12 October 2012 06:59

donino donino

Messages: 183
Registered: July 2011

Senior Member

Hi,

I never used the Eclipse debug perpspective, i wanted to give it a try in version 4.2.1 for my javascript event handlers. i followed this wiki:
- Open debug perspective
- Run->debug configurations->Add a report configuration
- I did not change the configuration suggested, so "run and render" mode

When i click on "debug" it opens the report parameter dialog, but i can't run the report, i get this exception for the first required parameter: "Value of required parameter [Year] is not specified", whatever i do.
index.php/fa/11821/0/

Though this report hasn't errors and runs correctly in the report design perspective.

I tried various debug configurations with a same result. Did i miss something? Is there a way to workaround this issue?

Thanks

Attachment: debug-perspective-issue.png
(Size: 48.51KB, Downloaded 538 times)

[Updated on: Fri, 12 October 2012 07:03]

Report message to a moderator

Re: Eclipse debug perspective issue with required report parameters [message #941699 is a reply to message #941039]

Fri, 12 October 2012 19:31

Jason Weathersby

Messages: 9167
Registered: July 2009

Senior Member

This looks like it may be a bug. Does it work with a report that has no parameters or a parameter that is not marked as required?

Jason

Report message to a moderator

Re: Eclipse debug perspective issue with required report parameters [message #942734 is a reply to message #941699]

Sat, 13 October 2012 20:58

donino donino

Messages: 183
Registered: July 2011

Senior Member

Hi Jason,

it appears this issue mainly involves combobox and listbox parameters, both static and dynamic. If a report contains only textbox parameters, it works. It seems it has something to do with a confusion between value text / display text, but i could not pinpoint the precise cause. I join a sample report wich highlights this problem.