-
Notifications
You must be signed in to change notification settings - Fork 9
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
UI always depends on a specific file on eclipse.org #8
Comments
Has this issue been resolved yet or is there a workaround for it? My team has encountered this issue while trying to start the HOBBIT GUI. |
The only solution is to grant internet access to the platform. Please note that this is required because of #9 anyway. As long as the platform controller requires internet access, the issue regarding the gui has a low priority. |
This issue is caused by the jetty configuration files. These xml files include |
@MichaelRoeder Can this issue be closed? The platform is not really useful without internet access. |
No, please leave it as it is. In the future, we would like to offer the platform without using our gitlab (#9). |
Because of this, UI is also unavailable when something is wrong with Right now the parser we use complains about a syntax error in http://www.eclipse.org/jetty/configure_9_3.dtd as it returns a redirect. See also: jetty/jetty.project#8738 |
It seems that your project cannot find the XML entities for System ID and Public ID that ship with the Jetty Jars. |
You are using an old version of Jetty ...
Jetty version 9.3.x was declared End of Life back back in mid 2020. Jetty versions 9.4.x are now at End of Community Support. You should be using Jetty 10.x, or Jetty 11.x |
It is not possible to start the plattform in a local network that has no internet connection because the GUI crashes.
This is caused by a XML parser that is called in
InternalResources.findKeycloakConfig(InputStream is)
. Adapting the XML parsing should fix this problem.The XML parser tries to access a
dtd
file that is defined in the beginning of the XML file:The text was updated successfully, but these errors were encountered: