| Summary: | "The parameter 'path' must not be null" when running RAP with Workbench | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Stefan Milchram <stefan.milchram> |
| Component: | Workbench | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P1 | ||
| Version: | 2.0 | ||
| Target Milestone: | 2.0 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Stefan Milchram
Apparently, we must ignore applications that doesn't have a path parameter. Another side-effect of this change is that an existing IApplication cannot be made available in RAP without modification. This was possible before. I'd suggest to change the way IApplications are mapped to paths and brandings as follows: In an entrypoint extension, we allow to specify the id of an IApplication extension alternatively to an EntryPoint class. To make an IApplication available in RAP, you have to provide an entrypoint extension that refers to its id. All related properties (path, brandingId) are configured in the entrypoint extension. Consequences: * We need to add an additional attribute to the entrypoint extension. * We don't evaluate IApplication properties, there's also no risk of collisions. * For every servlet path, there is exactly one entrypoint extension. * There's only one place to specify path and branding. |