java warning in responsive webhelp build when fix.external.refs.com.oxygenxml is set to true
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 56
- Joined: Wed Aug 08, 2018 10:23 pm
java warning in responsive webhelp build when fix.external.refs.com.oxygenxml is set to true
We've noticed that we're getting the following java warning in Oxygen 24.0 when we build responsive webhelp with fix.external.refs.com.oxygenxml set to true:
[WARN] Could not override the default file protocol handler
java.lang.reflect.InaccessibleObjectException: Unable to make field static java.util.Hashtable java.net.URL.handlers accessible: module java.base does not "opens java.net" to unnamed module @68c9d179
(rest of stack trace omitted for brevity)
The build continues and the output seems to be fine but we're wondering if this is a known issue? In that regard, this appears to be a consequence of upgrading from java 8 to java 16 (and higher) and can be suppressed by adding --add-opens java.base/java.net=ALL-UNNAMED as an argument to the JVM.
Thanks for any information you can provide
[WARN] Could not override the default file protocol handler
java.lang.reflect.InaccessibleObjectException: Unable to make field static java.util.Hashtable java.net.URL.handlers accessible: module java.base does not "opens java.net" to unnamed module @68c9d179
(rest of stack trace omitted for brevity)
The build continues and the output seems to be fine but we're wondering if this is a known issue? In that regard, this appears to be a consequence of upgrading from java 8 to java 16 (and higher) and can be suppressed by adding --add-opens java.base/java.net=ALL-UNNAMED as an argument to the JVM.
Thanks for any information you can provide
-
- Posts: 9473
- Joined: Fri Jul 09, 2004 5:18 pm
Re: java warning in responsive webhelp build when fix.external.refs.com.oxygenxml is set to true
Hi,
In Oxygen 24.1 we suppressed this error from being shown in the console by automatically adding --add-opens=java.base/java.net=ALL-UNNAMED when running DITA transformation scenarios.
When running with the " fix.external.refs.com.oxygenxml" parameter enabled Oxygen has its own pre-processing stage and has its own URL handlers for protocols like "file://" and if that command line parameter is not set, Oxygen is unable to install its protocol handler, the code falling back to the default Java protocol handler which should work just as well. So I also consider the problem is benign.
Regards,
Radu
In Oxygen 24.1 we suppressed this error from being shown in the console by automatically adding --add-opens=java.base/java.net=ALL-UNNAMED when running DITA transformation scenarios.
When running with the " fix.external.refs.com.oxygenxml" parameter enabled Oxygen has its own pre-processing stage and has its own URL handlers for protocols like "file://" and if that command line parameter is not set, Oxygen is unable to install its protocol handler, the code falling back to the default Java protocol handler which should work just as well. So I also consider the problem is benign.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Return to “DITA (Editing and Publishing DITA Content)”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service