I call a jasper report through an independent URL through which I pass one of the input controls needed to run the report.

E.g. http:// localhost:8080/jasperserver/flow.html?_flowId=viewReportFlow&standAlone=true&reportUnit=xyz&ParentFolderUri=abcd&j_username=xyz&j_password=xyz&parameter1=value1& . . .

As you can see in the URL, I pass the JasperServer username and password, reportUnit name and location and other mandatory parameters, along with the report input parameter, i.e., "parameter1" which can have a value like "value1".

I used a mandatory, read-only and visible input control for this input value. Its value would come from the URL, showed in the box but was read-only and hence could not be changed.

The report was working absolutely fine upto this point.

But the tragedy began when my client rejected this idea. He wanted a completely invisible input control to my report and the input value would be passed through the URL, just like illustrated above.

And then my client asked me to refer to this and made me work on cascading input controls.

Recently I added a cascading input control to this report. The input control type is a single select query, which utilizes two parameters that I pass to the report through the URL.

Now when the Jasper server responds to the URL with the input parameters, all the other static parameters work properly, except for the cascaded one.

When I click the select box of the cascaded input, I can see the desired options for a second, and then, it just goes empty while I'm viewing the select list.

But when I make the "Parameter1" input control visible, the cascading input control works!

And then I turn in invisible, the cascading input control turns into a beast that does things by itself and not listen to his master.

I am not able to understand why this is happening. Could anybody please provide me a solution to this?