manshack_one

I found in the documentation that I can add "&output=pdf" at the end of the url and get a pdf after the user enters the parameters in jasper server. now I'm going to try adding the parameters in the url and see if I just get the pdf.

I have some reports set up right now that are ran from a url link in the application. The username and password is hardcoded into the url and everything works fine. They are displayed a new window, they enter the 2 dates the report has parameters for and they get the report. At that point they can hit the pdf icon and print it out or save it. What I was hoping to be able to do is to pass those date parameters in the url. Can you do that? The next thing I'd love to be able to do is just pass the parameters and have a pdf file displayed instead of opening the jasper server window and exposing the jasper server website to them. I know you can do it by putting the report compilation into a java application and calling it with the parameters. I was just hoping there was an alternative in jasperserver to pass in the parameters (which would be gathered and formed using a funciton in the application where the url would be built) and just get the pdf back. Can that be done?

allright, nevermind. I just took another route and removed the rectangles. Then I spread out the column headers to cover the whole row and just set their background color doing the same for the corresponding fields. Worked out nicely.

Forgot to say my jasperserver version is 3.5. I'm using the Cherry landscape template in iReport 3.6 if that matters. I need to figure this one out. The report looks ugly without that color in there to separate the rows.

I used iReport 3.6 to create a simple wizard based report. I added some rectangles to the background of the column header to act as a background color. After uploading the report to jasper server the rectangles are not visible at all and I just see the original column headers with plain white background. The report displays correctly in iReport. Would Jasper have issues with the way you have to "layer" the shapes so they show behind the right objects?

using iReport 3.6.0 and I have a simple report that I've added two rectangles to the column header section that are different colors. They're sitting in the back and being used as visual indicator. Either way the report displays fine in iReport but when viewed on jasperserver the rectangles are not visible at all. The column header displays normally without the boxes behind it for color. Does it have anything to do with moving the boxes forward and backwards so they layer correctly? maybe jasperserver is disregarding that and putting them on the bottom where the labels cover them up completely?

So which JDBC version do you recommend using? I downloaded iReport 3.6.0 and have it running with the 5.0.7 driver as well as JasperServer 3.5.0 with the 5.0.7 driver. Should I stick with what I have or would it be less buggy to use a higher version JDBC driver on both sides?

Finally got it working! I ended up downloading 3.6.0 iReport to fix a bug where having compatibility mode on would delete my group footer band everytime you closed the report. I re-ran the report and verified everything is still on 5.0.7 jdbc driver. Then I replaced the query with this: SELECT * FROM call_detail WHERE CallDate = $P{ReportDate} and UPPER(call2) LIKE "COMPLETE" and UPPER(call1) NOT LIKE "THIRD PARTY IVR" and UPPER(Last) NOT LIKE "SECURUS" and UPPER(First) NOT LIKE "SECURUS" and DialedNumber NOT LIKE "8162437111" Basically it replaced all the alias parts of the query. Then I made sure the report name was identical between iReport and jasperserver's resource and label names (not sure if that made a difference or not). Then I published the report with the new query to a new folder on jasperserver and set up the input control again. Now it runs. I really think it had something to do with that query. It would seem that others would have similar issues though if they're using the query designer in iReport. Doesn't matter to me right now. It works. :) Thanks for all your time.

jar:file:/opt/jasperserver-3.5.0/apache-tomcat/webapps/jasperserver/WEB-INF/lib/mysql-connector-java-5.1.5.jar!/com/mysql/jdbc/Driver.class So it was hiding in the web-inf/lib directory. Verified it was using the 5.0.7 jar file but the report still gets the same error. I think it's something to do with the query structure and how it aliases everything. I think I'll copy that report and rewrite the query without the aliases. I'll let you know what I find out.

I renamed the one in tomcat to .bak and copied the 5.0.7 out there. Restarted jasperserver and it still says 5.1.5 when I run that report. where else would it be looking for the jar?

mysql-connector-java-5.0.7 sorry bout that. AFAIK both programs are using the bundled drivers.

mysql-connector-java-5.0.7 sorry bout that. thought i'd told it to use the datasource. AFAIK both programs are using the bundled jdbc drivers.

on Jasperserver: mysql-connector-java-5.1.5 3.5.0 in iReport: null 3.5.2

iReport version 3.5.2 JasperServer 3.5.0 In iReport I set the compatibility to 3.5.0 to force a downgrade on the report. I guess I don't see the relevance of the driver version though. If I'm using JDBC in Ubuntu to get to a mysql database and you're in windows using ODBC we're still seeing the same database. We just have different doors to go through. That being said I setup a data source in jasperserver that points to the database and in iReport during publishing of the report I chose to use that datasource from the repository. I've tried it the other way also and using the datasource from iReport. Either way it gets the same error. How do I find out which jdbc driver version I have? iReport is on windows, jasperserver is on linux.

Both using com.mysql.jdbc.Driver

As far as I know, yes. I'll double check it but I'm pretty sure it's the same mysql jdbc on the server and the pc. Be Right Back with the answer.

no ideas? Seems like it would be a common problem.

Any ideas?

I created a very simple report in iReport. Here's the query: SELECT call_detail.`Unit` AS call_detail_Unit, call_detail.`DialedNumber` AS call_detail_DialedNumber, call_detail.`Rate` AS call_detail_Rate, call_detail.`Minutes` AS call_detail_Minutes, call_detail.`Last` AS call_detail_Last, call_detail.`First` AS call_detail_First, call_detail.`Revenue` AS call_detail_Revenue, call_detail.`Commission` AS call_detail_Commission FROM `call_detail` call_detail WHERE call_detail.`call2` LIKE "Complete" It compiles and runs fine in iReport. However, when I publish it to jasperserver and try to run it I get this error: com.jaspersoft.jasperserver.api.JSExceptionWrapper: net.sf.jasperreports.engine.JRException: Unknown column name : call_detail_Unit Both iReport and jasperserver are pointing to the same datasource. I have a feeling it's something to do with the alias it's using. However I've tried changing the query to leave out the alias's and the dot notation on the columns and get the same error. I've also tried creating the report and instead of pushing it to the server, going into jasperserver and pulling it in using the new report wizard. Same result either way. How do I get them to talk to the database the same way?

I created a very simple report in iReport. Here's the query: SELECT call_detail.`Unit` AS call_detail_Unit, call_detail.`DialedNumber` AS call_detail_DialedNumber, call_detail.`Rate` AS call_detail_Rate, call_detail.`Minutes` AS call_detail_Minutes, call_detail.`Last` AS call_detail_Last, call_detail.`First` AS call_detail_First, call_detail.`Revenue` AS call_detail_Revenue, call_detail.`Commission` AS call_detail_Commission FROM `call_detail` call_detail WHERE call_detail.`call2` LIKE "Complete" It compiles and runs fine in iReport. However, when I publish it to jasperserver and try to run it I get this error: com.jaspersoft.jasperserver.api.JSExceptionWrapper: net.sf.jasperreports.engine.JRException: Unknown column name : call_detail_Unit Both iReport and jasperserver are pointing to the same datasource. I have a feeling it's something to do with the alias it's using. However I've tried changing the query to leave out the alias's and the dot notation on the columns and get the same error. I've also tried creating the report and instead of pushing it to the server, going into jasperserver and pulling it in using the new report wizard. Same result either way. How do I get them to talk to the database the same way?

It's a bug. Create the project and job without spaces in the name. I'm up and working now.

I think I'll move this question over to the Talend forums since it's actually their product. I'll try and remember to post back a link.

I'm running JasperETL on my windows xp workstation. I can get through project creation and business model creation but when I try and create a new job I get this error when it tries to open it. Any ideas? org.talend.designer.runprocess.ProcessorException: Folder within .Java project not founded at org.talend.designer.runprocess.java.JavaProcessor.initCodePath(Unknown Source) at org.talend.designer.runprocess.java.JavaProcessor.initPaths(Unknown Source) at org.talend.designer.runprocess.Processor.setContext(Unknown Source) at org.talend.designer.runprocess.ProcessorUtilities.getProcessor(Unknown Source) at org.talend.designer.core.ui.AbstractMultiPageTalendEditor.createPage1(Unknown Source) at org.talend.designer.core.ui.AbstractMultiPageTalendEditor.createPages(Unknown Source) at org.talend.designer.core.ui.MultiPageTalendEditor.createPages(Unknown Source) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:310) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:306) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608) at org.eclipse.ui.internal.PartStack.add(PartStack.java:499) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103) at org.eclipse.ui.internal.PartStack.add(PartStack.java:485) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112) at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217) at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207) at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:779) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:678) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:639) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2817) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2643) at org.talend.designer.core.ui.action.EditProcess.doRun(Unknown Source) at org.talend.repository.ui.actions.AContextualAction$2.run(Unknown Source) at org.talend.repository.RepositoryWorkUnit.executeRun(Unknown Source) at org.talend.repository.model.AbstractRepositoryFactory.executeRepositoryWorkUnit(Unknown Source) at org.talend.repository.model.ProxyRepositoryFactory.executeRepositoryWorkUnit(Unknown Source) at org.talend.repository.ui.actions.AContextualAction.run(Unknown Source) at org.talend.repository.ui.actions.RepositoryDoubleClickAction.run(Unknown Source) at org.talend.repository.ui.views.RepositoryView$7.doubleClick(Unknown Source) at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:799) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:797) at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1419) at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1173) at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:237) at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:234) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:295) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.talend.rcp.intro.Application.start(Unknown Source) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236)