Skip to content
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

Ensure that org.apache.axis is in the org.eclipse.birt.engine.runtime #1835

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

merks
Copy link
Contributor

@merks merks commented Aug 5, 2024

  • Also add org.eclipse.birt.chart.device.pdf which the only plugin included by org.eclipse.birt.chart.osgi.runtime but not by org.eclipse.birt.engine.runtime.

- Also add org.eclipse.birt.chart.device.pdf which the only plugin
included by org.eclipse.birt.chart.osgi.runtime but not by
org.eclipse.birt.engine.runtime.
@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

@speckyspooky

I built locally to verify that axis in included with this change:

image

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

I also added the one bundle specified in only in the chart runtime:

image

So we could simplify the runtime product to a single feature in the future.

@merks merks merged commit 0b75c7f into master Aug 5, 2024
4 checks passed
@speckyspooky
Copy link
Contributor

Yes, I see. I will retest directly after the build is done to verify the result.

@merks merks deleted the pr-runtime-axis branch August 5, 2024 08:04
@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

@speckyspooky

Yes, perhaps something else is missing. But we can quickly add anything that might be missing.

@speckyspooky
Copy link
Contributor

Retest is done and failed:

Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/birt]]
	at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:419)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:186)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:687)
	... 37 more
Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPException
	at java.base/java.lang.Class.getDeclaredFields0(Native Method)
	at java.base/java.lang.Class.privateGetDeclaredFields(Class.java:3297)

grafik

@speckyspooky
Copy link
Contributor

My test case is very simple and based on the Tomcat installation and try to start the BIRT-viewer as web-applicattion.

So I copy "WebViewerExample" to the tomcat "webapps" folder, rename it to "birt" and try to start my Tomcat.
If the Tomcat is running I check the running applications and finally to start the birt-viewer to create our test reports.

But currently the "birt"-web-application is not starting, "axis" seems to be solved, but "javax.xml.soap" now is missing.

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

I'm surmising this is caused by the ant scripts not copying the right files because the file name has changed.

I see this

$find . -name *apache.axis*
./ReportEngine/platform/plugins/org.apache.axis_1.4.1.v20231107-0937.jar
./war/WEB-INF/lib/org.apache.axis_1.4.1.v20231107-0937.jar
./war/WEB-INF/platform/plugins/org.apache.axis_1.4.1.v20231107-0937.jar
./WebViewerExample/WEB-INF/lib/org.apache.axis_1.4.1.v20231107-0937.jar
./WebViewerExample/WEB-INF/platform/plugins/org.apache.axis_1.4.1.v20231107-0937.jar

$find . -name *soap*
./ReportEngine/platform/plugins/jakarta.xml.soap-api_1.4.2.jar
./war/WEB-INF/platform/plugins/jakarta.xml.soap-api_1.4.2.jar
./WebViewerExample/WEB-INF/platform/plugins/jakarta.xml.soap-api_1.4.2.jar

I think this needs to change:

image

I'll build locally first to verify this works before creating another PR.

I'll see if I can understand this Tomcat thing to try it myself.

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

Is there a certain version of Tomcat I should install?

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

I guessed it was 9.x.

I got it to this point:

image

I think another issue with the jar name being different...

@speckyspooky
Copy link
Contributor

I tested Tomcat 9.0.88

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

I got further fixing the ant scripts, but now the clues are less helpful:

image

I used 9.0.91.

Can you say when was the last time that you tested the web application? The major cleanup with 3 weeks ago; was it tested between today and that point in time? I really rely on the tests to tell me if something is broken.

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

I get the same result using birt-runtime-osgi-4.16.0-202406141054.zip so I don't think I'm really testing properly/correctly.

This looks fine:

image

Any idea what I might be doing wrong with my testing?

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

Using Java 21 makes no difference.

@speckyspooky
Copy link
Contributor

I have retested our release BIRT 4.16 (Version: birt-runtime-osgi-4.16.0-202406141054),
the result is perfect and our demo reports can be created.

grafik

@speckyspooky
Copy link
Contributor

I cannot say when I tested an OSGi-version of BIRT 4.17 the last time with success.
I was triggered based on your dependency change of the "viewer" to test it today.

I must take a look if I have an old 4.17 version at home.

@merks
Copy link
Contributor Author

merks commented Aug 5, 2024

Hmm, I forgot to hit enter on my previous observations. The non-OSGI runtime works for me for both 4.16 and 4.17 but the OSGi runtime doesn't work for me for either version.

image

So hopefully you have good luck with both version for 4.17 when the master build finishes in about 1/2 hour.

@speckyspooky
Copy link
Contributor

I keep you updated after my retest.

@speckyspooky
Copy link
Contributor

Retested with BIRT 4.17 (version: birt-runtime-osgi-4.17.0-202408051540) and it is running,
the demo reports can be created successfully.

Thanks for the dependency changes here to solve the topic!

grafik

@speckyspooky speckyspooky added this to the 4.17 milestone Aug 5, 2024
@speckyspooky speckyspooky added the Dependencies Pull requests that update a dependency file label Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants