| Summary: | IApplication missing parameter support | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Paul Bilnoski <bilnoski> | ||||
| Component: | Workbench | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | ASSIGNED --- | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | ||||||
| Version: | 1.3 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 175986 [details]
IApplication implementation to use the argument
|
Build Identifier: 1.3 Parameters given to the "run" element in an application extension point are not evaluated. It is optional that an IApplication instance may also implement IExecutableExtension to be passed static arguments. <extension id="brokey" point="org.eclipse.core.runtime.applications"> <application visible="true"> <run class="bug.rap.applicationargs.Application"> <parameter name="configParam" value="custom argument"> </parameter> </run> </application> </extension> This is useful when the IApplication implementation is complex and could benefit from argument injection instead of being subclassed when multiple entry points are defined on the same RAP application. Reproducible: Always