Changing datasource of reports in a loop only works for first report.

Question

Hi,
I have code that loops through a list of reports to change the datasource and save the change in the report. The idea is that this can be done at build time so time taken at runtime is only for opening the report and running it.
The problem is that the first iteration of the loop works, and any further ones don't. Apart from closing the client document is there anything else that should be explicitly closed? I don't retrieve any ReportSource from the Client Document so I shouldn't need to dispose of that...I don't think. In particular is there something that should be done to the databaseController retrieved from the clientDoc after each loop?
The code goes like the below:
for(File report : reports){
     System.out.println("Preparing report: " + report.getAbsolutePath());
     ReportClientDocument clientDoc = CRJavaHelper.getReportClientDocument(
               report.getAbsolutePath());
     CRJavaHelper.replaceDBConnection(clientDoc, props);
     clientDoc.close();
     System.out.println("Report " + report.getAbsolutePath() + " prepared.");
getReportClientDocument does this:
ReportClientDocument clientDoc = new ReportClientDocument();
clientDoc.setReportAppServer("inproc:jrc");
clientDoc.open(fullPath,
          OpenReportOptions.openAsReadOnly.value());
return clientDoc;
replaceDBConnection does the following:
DatabaseController dc = clientDoc.getDatabaseController();
logonDataSource(dc, username, password);
prepareReport(dc, schema);
ConnectionInfos cis = dc.getConnectionInfos(null);
for (IConnectionInfo oldci : cis) {
     IConnectionInfo newci = new ConnectionInfo();
     newci.setKind(ConnectionInfoKind.SQL);
     newci.setAttributes(propBag);
     newci.setUserName(username);
     newci.setPassword(password);
     dc.replaceConnection(oldci, newci, null, DBOptions._useDefault
               + DBOptions._doNotVerifyDB);
SubreportController src = clientDoc.getSubreportController();
IStrings strs = src.getSubreportNames();
Iterator<?> it = strs.iterator();
while (it.hasNext()) {
        String name = (String) it.next();
     ISubreportClientDocument subreport = src.getSubreport(name);
     DatabaseController sdc = subreport.getDatabaseController();
     cis = sdc.getConnectionInfos(null);
     for (IConnectionInfo oldci : cis) {
          IConnectionInfo newci = new ConnectionInfo();
          newci.setAttributes(new PropertyBag(propBag));
          newci.setUserName(username);
          newci.setPassword(password);
          sdc.replaceConnection(oldci, newci, null, DBOptions._useDefault
                    + DBOptions._doNotVerifyDB);
clientDoc.save();

Answer 1

What's the URL for the site where you are using this?  Offhand, it looks like it should work with your first example so you are either placing the script before those elements are loaded or you might try wrapping your current javascript inside the:
$(document).ready(function() {
--- your existing javascript here
This make sure the code runs once all the html is loaded on the page.  Without seeing a URL and debugging with the js console in Chrome I can't give you a solid answer.
But, I do know that you can probably do this with a lot less markup.  Once we figure out what the actual problem is I have a better solution mocked up for you on jsfiddle.
When looking at my HTML code on jsfiddle, please realize I setup some dummy HTML and removed your tags and added actual values which would be output by your tags.  The main thing I did was remove the whole div.more-selection and instead, added a "data-is-selected" attribute on your div.more-option element.  Then, in my javascript for each div.my-option element on the page, we loop through them, find the value of that data attribute and hide that div if it's less than 1 (or 0).
Here's the fiddle for you to look at:  http://jsfiddle.net/thetrickster/Mfmdu/
You'll see in the end result that only two divs show up, both of those divs have data-is-selected="1".
You can try pasting the javascript code near the closing </body> tag on your page and make sure to wrap my js inside a <script> tag, obviously.  My way is neater on the markup side.  If you can't get it to work it's likely a jquery conflict issue.  My version is using the $(document).ready() method to make sure all the code is loaded before it runs.
Best,
Chris