Ah sorry. The documentation confused me. Where it says "We check that the type of DATA column is the most suitable type .." I thought that the "we" meant OpenXava. It might be clearer if it said that the user has to to do this. Might also be worth annotating the data field with @Length though I see conflicting reports about whether this works. Martin
This might be a known problem? I'm seeing the data column of oxfiles created as TINYBLOB type, when it should be LONGBLOB. Can be fixed by altering the table but would be good if it was created correctly.
If I take the report that works and stick in a Thread.sleep() for 10 seconds after calling super.execute() it seems to break it in the same way as the other one. I think you might be able to reproduce it by doing something similar. I would suspect a race condition or timeout somewhere perhaps.
I've reproduced it on a different computer. Now I need to see if I can create something simple that shows the same problem. I have a vague feeling it might be the time taken to generate the report - about 30 seconds for the action to complete. The one that works takes about 8 seconds.
I've reproduced it on a different computer. Now I need to see if I can create something simple that shows the same problem. I have a vague feeling it might be the time taken to generate the report - about 30 seconds for the action to complete.
I've reproduced it on a different computer. Now I need to see if I can create something simple that shows the same problem.
I'll try but not sure how reproducible this is going to be. One thing I noticed is that with IForwardAction the browser tab opens straight away and you wait for the report to appear. With IMultipleForward the tab opens at the end of the process. I realized that ModuleManager / Module handle the single URI case before the multiple one so I have a workround by using my own JasperConcatReportBaseAction. Martin
OK, more debugging. It seems to be something related to IMultipleForwardAction handling. If I replace JasperMultipleReportBaseAction with a copy that implements IForwardAction instead then the concat report works. This is obviously not a proper solution as some multiple reports return more than one URI but I think it might help to narrow it down. I currently don't understand why it works for one report but not the other one and I haven't found anything wrong trying to debug the request flows.