| Summary: | [Tooling] Validate Jetty bundles selected | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Beyhan Veliev <beyhan.veliev> |
| Component: | Tools | Assignee: | Project Inbox <rap-inbox> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | rsternberg |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Beyhan Veliev
We should remember to include Jetty 7 in the validated bundle id pattern, as the 1.4 Tooling might also be used with later target platforms. Another possible solution here beside bundle id pattern validation could be to ping the server on "locahost:port". Currently, we are doing it when a launch configuration is started and we open the browser when the server is there. We have also an timeout for the server. When the timeout is exceeded and there is no server listening on "locahost:port" we just open the browser. What about to show an warning dialog in this case which says e.g. "Hey something is wrong with your server. May be you forgot to select the Jetty bundles". IMO this is a better solution because we aren't bound with some Jetty bundle ids and can react generally to server problems. |