| Summary: | [Tooling] Branding defaultEntrypointId browser should honor IApplication extensions | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Benjamin Wolff <eclipse> |
| Component: | Tools | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | artur.kronenberg, elias |
| Version: | 1.4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 221540 | ||
| Bug Blocks: | |||
|
Description
Benjamin Wolff
This bug seems to be blocked by bug Nr. 221540 for now. Currently it seems to be only possible to reference one identifier and we'd need to reference two. As a workaround I propose to use the type String instead of Id (in the extension point). The problem is that when using an application id, one gets a warning "referenced identifier 'app.id' could not be found", because the tooling looks for an entry point id. This would be solved by using a String. Drawback: no 'Browse' button. I agree with the suggestion in comment 2. Since both entrypoint ids and an application extension ids are admissible as values for this attribute, an identifier that restricts the values to entrypoint ids only is wrong. BTW, the application attribute to the o.e.core.runtime.products extension point also accepts Strings instead of identifiers, so it's not completely uncommon. Applied change to CVS HEAD. In RAP 2.0 there is no more defaultEntrypointId in branding. Close as WONTFIX. |