You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Apache Hop project utilizes an embedded Jetty server, which requires programmatic configuration for web server functionalities, including security handling with Keycloak. This setup poses challenges in environments that prefer or exclusively support WAR deployments, common in enterprise setups that utilize application servers like Tomcat or WildFly.
Feature Request
I propose adding support to export the Hop Web Server as a .war file. This change would simplify deploying on standard servlet containers or application servers and streamline the integration with security frameworks like Keycloak, which are more traditionally configured via web.xml.
Issue Priority
Priority: 3
Issue Component
Component: Hop Server
The text was updated successfully, but these errors were encountered:
What would you like to happen?
Description
Currently, the Apache Hop project utilizes an embedded Jetty server, which requires programmatic configuration for web server functionalities, including security handling with Keycloak. This setup poses challenges in environments that prefer or exclusively support WAR deployments, common in enterprise setups that utilize application servers like Tomcat or WildFly.
Feature Request
I propose adding support to export the Hop Web Server as a .war file. This change would simplify deploying on standard servlet containers or application servers and streamline the integration with security frameworks like Keycloak, which are more traditionally configured via
web.xml
.Issue Priority
Priority: 3
Issue Component
Component: Hop Server
The text was updated successfully, but these errors were encountered: