| Summary: | RWT OSGi integration does not work when IEntryPoint is an inner class | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Holger Staudacher <holger.staudacher> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | fr.appel | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 2.0 M1 | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Holger Staudacher
Was your inner class declared as static? If not, there's probably nothing we can do about it, since the IEntryPoint instance is created using reflection. And it would be a problem of the EntryPointManager anyway. So it would be helpful to have a Configurator example that makes this problem reproducable. If my assumptions are right there might be a possibility to provide a more speaking error message, but that would all I can think of at the moment... Created attachment 199311 [details]
Example Project
I attached an example project to reproduce this error. You are right, the inner class was not static. The archived project contains a launch config which starts on port 9292. You can use the entry point name "osgi". HTH
+1 for a more speakable error message.
Added meaningful exception messages in 6b2f8ec87fec211de25300e43b44a21f9176f654. |