-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrapped java.lang.IllegalAccessException when trying to make https request #1409
Comments
This is probably a problem with Rhino, the JavaScript engine that Birt uses. ... looks related. If it indeed is the same problem it should be fixed in Rhino now. I do not know which version of Rhino that Birt 4.13 uses, nor, if we have updated that dependency with Birt 4.14, but generally I would say: Test this in a 4.14 build and see if it works there. |
It looks like we are using Rhino 1.7.10 in Birt 4.14. The issue mentioned above is solved in Rhino 1.7.14, so we will need to update Rhino to solve this issue. |
Yes, orbit itself is still "stuck" on this older versions I am in the process of restructuring Orbit so that we can more easily and automatically update to newer dependency versions: https://github.com/orgs/eclipse-orbit/discussions/49 So I will get around to looking at this dependency in the coming weeks... |
This is basically the same as #1138, a result of the modularization in Java 9 and is now enforced by default in Java 17 (this is probably not exactly correct, but should suffice as an explanation). Two different workaround are possible (I tested both for similar problems): Either you can write a little Java class that implements the functionality of the script and call this Java class from the script. Or you can add VM arguments to your BIRT Java process which allow the classes to be used. Eg. for a report which creates charts using JFreeChart I had to add
The packages you have to specify can be seen in the error messages. In your case I guess it should read
Maybe this results in a similar error message with different pacakes/classes, so maybe you have to add more |
Yes, the core problem is this part of the stack trace "(in module java.base)" But Rhino doesn't know that he has to search into a "module" therefore the jars cannot be loaded. I have special reports too which use Web-Requests and currently I plan to create report-jars as external resources to handle this problem. But it would be great if I can avoid this step. |
Workaround option: tested The result is that the configuration is working. For the configuration I added the 2 following lines
The both lines solved the problems:
and
Perhaps this would be realy an option at first to get your report running. I see you work with JSON which is good. |
Adding those options did get me further but this time it's throwing this:
|
I guess this is an error of your REST call, unrelated to the original issue or the workaround. |
I have tested your script in a light modified version with one of my test pages: "https://httpbin.org/post"
|
Closing. |
We are making https requests in our data sources to fetch data from our APIs.
We've been using following code to achieve this:
Yesterday we downloaded new designer from 4.13 release and now running report viewer throws following exception:
The text was updated successfully, but these errors were encountered: