RaulBSC opened a new issue, #8914: URL: https://github.com/apache/hop/issues/8914
### Apache Hop version? 2.19.0 ### Java version? 21 ### Operating system Windows ### What happened? When configuring Hop Server, the webAppName property can be specified in hop-server.xml. However, changing this value does not seem to change the context path used by Hop Server. For example, when configuring: <webAppName>myapp</webAppName> I would expect the Hop Server endpoints to be exposed under a context path based on myapp, for example: http://<host>:<port>/myapp/status/ However, the server still exposes its endpoints using the default /hop/ context: http://<host>:<port>/hop/status/ Expected behavior Changing webAppName in hop-server.xml should either: change the context path used by the Hop Server web application, or if webAppName is not intended to control the context path, its actual purpose should be documented. Actual behavior Changing webAppName does not appear to affect the /hop/ context path. Question What is webAppName currently used for in Hop Server? If the value is not used to configure the web application's context path, having it in hop-server.xml is confusing and its purpose should probably be clarified. ### Issue Priority Priority: 3 ### Issue Component Component: Hop Server -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
