Scheduled Jasper Server Job isn't passing parameters#82
Open
paawak wants to merge 5 commits intoJaspersoft:masterfrom
Open
Scheduled Jasper Server Job isn't passing parameters#82paawak wants to merge 5 commits intoJaspersoft:masterfrom
paawak wants to merge 5 commits intoJaspersoft:masterfrom
Conversation
…xt from json string
Contributor
|
The bug can not be reproduced on the latest version of client (6.1.4). Please, try this version and reopen the issue. |
Contributor
|
Thanks for pointing to the issue. We fixed it in a bit another way. Please try the latest release version and fill free to reopen an issue if something doesn't work. |
Author
|
Tried with 6.2.2. The issue persists. The job is created with the parameters set to null. Thanks, |
|
This is still an issue in 6.3.1. How do I get around this problem? |
|
clientSessionForAsynchronousRequest.jobsService().scheduleReportWithHack(job) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We are using the jrs-rest-java-client, version 5.5.0 (https://github.com/Jaspersoft/jrs-rest-java-client ) to schedule a
Job on the Jasper (Tomcat) Server. The problem is, though the job is created on the server, the report parameters are
all null.
This is the client code:
private Session clientSessionForAsynchronousRequest;
private void scheduleJob(String reportUri, Map parameters) {
Job job = new Job();
job.setLabel("New Job for ISS Report");
job.setDescription("New Job for the report template: " + reportUri);
JobSource jobSource = new JobSource();
jobSource.setReportUnitURI(reportUri);
}
However, we have a bad work-around, by changing the JobsService in jrs-rest-java-client. The above code works if I replace:
long jobId = clientSessionForAsynchronousRequest.jobsService().scheduleReport(job);
With:
long jobId = clientSessionForAsynchronousRequest.jobsService().scheduleReportWithHack(job);
// long jobId = clientSessionForAsynchronousRequest.jobsService().scheduleReport(job);
Also, I have forked the project on git-hub, and you will find my changes here:
https://github.com/paawak/jrs-rest-java-client
Thanks,
Palash.