I cannot get the example applet to work in my chrome browser on mac os
I tried cloning the example here - https://github.com/leaningtech/cheerpj-meta/tree/main/examples/Pitch-Applet
But am not able to get it to run
GitHub
cheerpj-meta/examples/Pitch-Applet at main · leaningtech/cheerpj-meta
Run Java 8 applications, libraries, applets, Java Web Start, and Oracle Forms on the web without legacy plugins. - leaningtech/cheerpj-meta
29 Replies
The example is already integrated with CheerpJ, which means the applet runner is not required and will actually cause conflicts.
even with the extention disabled i get the same view
im using an m2 pro on mac os 15.2 and chrome 131.0.6778.265 (Official Build) (arm64)
It's certainly not a platform issue. CheerpJ is completely cross platform.
on chrome console i see these logs
on local i see
❯ python3 -m http.server 8000
Serving HTTP on :: port 8000 (http://[::]:8000/) ...
::1 - - [15/Feb/2025 15:30:00] "GET /index.html HTTP/1.1" 304 -
::1 - - [15/Feb/2025 15:30:02] code 404, message File not found
::1 - - [15/Feb/2025 15:30:02] "GET /index.service.worker.js HTTP/1.1" 404 -
::1 - - [15/Feb/2025 15:30:05] "GET /index.html HTTP/1.1" 304 -
::1 - - [15/Feb/2025 15:30:07] code 404, message File not found
::1 - - [15/Feb/2025 15:30:07] "GET /index.service.worker.js HTTP/1.1" 404 -
::1 - - [15/Feb/2025 15:30:37] code 404, message File not found
::1 - - [15/Feb/2025 15:30:37] "GET /index.service.worker.js HTTP/1.1" 404 -
::1 - - [15/Feb/2025 15:32:32] "GET /index.html HTTP/1.1" 304 -
::1 - - [15/Feb/2025 15:32:35] code 404, message File not found
::1 - - [15/Feb/2025 15:32:35] "GET /index.service.worker.js HTTP/1.1" 404 -
Can you check if you have other extensions or previously installed service workers that are breaking CheerpJ?
index.service.worker.js is not part of CheerpJlet me try running on a guest profile in chrome so it wont use any extensions
whats the proper way to serve the index.html file? is using python server like above correct
I also noticed logs about
lockdown-install.js which is not part of CheerpJ
The python HTTP server is ok
Any server supporting HTTP byte ranges is sufficient
❯ python3 -m http.server 8000
Serving HTTP on :: port 8000 (http://[::]:8000/) ...
::1 - - [15/Feb/2025 15:35:48] "GET /index.html HTTP/1.1" 200 -
::1 - - [15/Feb/2025 15:35:49] code 404, message File not found
::1 - - [15/Feb/2025 15:35:49] "GET /favicon.ico HTTP/1.1" 404 -
Can you check the network tab?
it seems to keep fetching rt.jar
CheerpJ is still loading, it seems you have a very poor network connection, or potentially you might be located in mainland China where our CDN does not operate
oh weird, no im in austin texas in the US
is there a loading screen it can show instead of saying the applets not supported in the env?
it works now though thanks
CheerpJ is correctly loading, but the CDN is being very slow. It quite likely it will run faster from the second access on
There is a loading screen that is displayed before any Java window is creased. It's quite possible the window was created and not populated though.
yah cause even on second run its not using any cached resources its refetching and not showing a loading screen, but from network tab i can see it is trying to load
eventually it gets to this screen
before it loads the app
Please follow this instructions to export a HAR file: https://cheerpj.com/docs/guides/cheerpj-debug#extracting-a-har-file
Leaning Technologies Developer Hub
Debugging CheerpJ - CheerpJ Documentation
How to properly debug CheerpJ in the browser
The CDN is misbehaving here, but everything looks correct in our upstream server and my location
ok thanks
is there a way to see system.out.println logs from java in the console or anywhre to debug things
once i got back to better wifi load times is better now
System.out is automatically directed to the browser console, unless there has been application side overrides of output stream
I would still ask you if you could record the HAR to help us understand if there is something weird going on at the CDN levelSure here you go
Thanks, the behavior seems now normalized and equivalent to what I see locally. The long loading times from your previous screenshot are not visible anymore. I've closed the issue, for further discussions please consider using the #cheerpj channel, so that other members of the community can help as well