benu

Hi hozawa - thanks for your note. It turns out that the problem is with the host application server, Liferay running on Tomcat. It appears that the underlying theme and related CSS are getting applied to the custom portlet we developed to render the reports (using visualize.js). We're struggling with how to prevent this CSS from getting applied to the portlet - no luck there, yet. But, it does NOT appear to be a problem with Jaspersoft technology. So, I consider this resolved with respect to Jaspersoft. Thanks again, Ben

Additional information: Looks like visualize.js is taking the data, shoving it into the Text element, and when the line of text hits the right margin of the element, it inserts a <br></br> pair of tags. This seems to be what's causing the extra spacing. Why does visualize.js not use a paragraph tag for rendering the element?

We're using visualize.js successfully now - great approach to embedding reports in our Liferay app. However, I've hit a rendering issue that feels like a bug: When a report is rendered via visualize.js, the text in Text elements has additional space between the lines. There also seems to be a few pixels of space between the column band and the first group band, but the problem does NOT appear to be a band rendering issue, as we get extra space between lines of text within a single Text element. This bug is not evidenced in the export formats (.PDF, .DOCX, etc.) - reports look great on export. So - bug in the visualize.js code? Would someone please advise? Jaspersoft - shall I file this as a bug? Thanks, Ben

I've got a situation where I want to run one report with different data sources based on environment/context. For example, when in development, we want to tell visualize.js to access data in the development environment; when in production, we should pass in the production datasource. This was possible using the JRViewer; how do I do it with visualize.js? Thanks in-advance for any suggestions. -Ben

Hi Gowtham. While I can't explain the reasons why, I can confirm that integrating the visualize.js Javascript with our web server did solve the problem. The explanation that Sherman provided above re: iFrams and cross scripting seems to be the fundamental issue. Good luck! -Ben

Can you provide a little more context, i.e. the script that you're using to call up your report? -Ben

Hi Gene, Thanks very much for the corroboration and JSFiddle - working great, now. On to implementing in our Liferay app. Thanks, and regards, Ben

Sherman - astute observation: yes, this simple HTML page was just on my file system and I was opening it locally in my browser. Executing it in JSFiddle worked great. There must have been another issue integrating visualize.js into our Java web app, so we'll dig back into that - knowing that a proper test can't be done via the local file system. Thanks very much for your suggestion! -Ben

Thanks for your suggestions; unfortunately, these did not work. I'm making the assumption that if any of these parameters were actually incorrect, or missing, the API would have returned an explicit error message (or, it *should* have done, anyway!). -Ben

Finally, when my test page renders in Firefox, I get this in the browser debugger: "16:09:36.761" "[EasyXDM]" "[DEBUG] -" ": easyXDM present on 'file:/LOCAL_PATH_TO_MY_TEST_HTML_FILE/POC_visualize.html" visualize.js:63 "16:09:36.766" "[easyXDM.Rpc]" "[DEBUG] -" "constructor" visualize.js:63 "16:09:36.766" "[EasyXDM.{Private}]" "[DEBUG] -" "preparing transport stack" visualize.js:63 TypeError: t is null visualize.js:63 "16:09:36.766" "[EasyXDM.{Private}]" "[DEBUG] -" "resolved url 'http://MY.SERVER.org/jasperserver-pro/xdm.html?logEnabled=true&logLevel=debug'" visualize.js:63

Please ignore the span tags that this forum wrapped around my HTML page code...thanks.

We've just launched a copy of JRS via the AWS offering (ami-0e0fff66), and the basic operations work fine, i.e. report execute from the UI with no problems. However, when we try to render them using visualize.js, we get nothing except a cryptic error from the browser debugger: Uncaught TypeError: Cannot read property '2' of null There's a little more error context, which I will include if anyone responds to this post. The web page & script look like this: <!DOCTYPE html><html><head><script src="http://my.server.org/jasperserver-pro/client/visualize.js?logLevel=debug"></script><title>My Report</title></head><body><script>visualize({auth: {name: "reporting",password: "somepassword"}}, function (v) {var report = v.report({resource: "/public/Samples/Reports/9.CustomerDetailReport",container: "#container"});});</script><div id="container"></div></body></html> Pretty straightforward. We get nothing in the catalina.out nor jasperserver.log logs. We really don't have a clue why there's no response from the server. We do get the visualize.js page returned if we call it in the browser directly, i.e. http://my.server.org/jasperserver-pro/client/visualize.js, so I know it's accessible. And, as I mentioned, the reports run fine from the web UI. Would someone point us in the right direction, please - even if just to tell us how to gather more information about the problem? Thanks, Ben

Hi Hozawa. Thanks for the suggestion, but we're a community edition user, and I don't see a v5.6.1 release available to the community yet. If I'm mistaken, please add a comment to this post with a link to it! Thanks, Ben

Oh, and I found this link: http://community.jaspersoft.com/sites/default/files/bug_files/jasperserver_3.log...so I know that someone else has reported this recently, but I can't find the actual problem report.

I just did a .WAR file install of v5.6.0 with an existing Tomcat 7 and MySQL repo. It went swimmingly, with the UI coming right up and no errors. However, I can't get any reports to run. I deployed a dirt-simple report, but the UI just hangs with the "Please wait; loading" screen. When I cancel, I get this error in the logs: 2014-09-18 17:37:43,390 ERROR DiskStorageFactory,connection%002edescriptions.data:495 - Disk Write of 79d1aab1-2a04-4b48-a696-d33799e70ad5 failed: java.io.NotSerializableException: com.jaspersoft.jasperserver.remote.connection.ConnectionsManager$ConnectionDataPair at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:422) at net.sf.ehcache.Element.writeObject(Element.java:835) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:940) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at net.sf.ehcache.util.MemoryEfficientByteArrayOutputStream.serialize(MemoryEfficientByteArrayOutputStream.java:97) at net.sf.ehcache.store.disk.DiskStorageFactory.serializeElement(DiskStorageFactory.java:405) at net.sf.ehcache.store.disk.DiskStorageFactory.write(DiskStorageFactory.java:384) at net.sf.ehcache.store.disk.DiskStorageFactory$DiskWriteTask.call(DiskStorageFactory.java:485) at net.sf.ehcache.store.disk.DiskStorageFactory$PersistentDiskWriteTask.call(DiskStorageFactory.java:1088) at net.sf.ehcache.store.disk.DiskStorageFactory$PersistentDiskWriteTask.call(DiskStorageFactory.java:1072) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) I'm stuck - no idea how to proceed. The machine (and JVM) have ample resources (followed the config requrements in the install guide). Would someone point me in the right direction, please? Thanks in-advance. -Ben