Bugzilla – Full Text Bug Listing
| Summary: | [OSGi Integration] OSGi Http Service configured twice when registering two service instances of org.eclipse.rwt.application.ApplicationConfigurator | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Zahn <ralf.zahn> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | fr.appel, holger.staudacher, ralf.zahn |
| Version: | 1.5 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Ralf Zahn
If you want to register two ApplicationConfigurators at the same HttpService you have to set either a different contextName for both configurations in ApplicationLauncher#launch(...) or use an appropriate service property. Unfortunately the latter is not implemented yet :-( I will do this ASAP. This way the applications can work properly isolated. Starting two ApplicationConfigurators with the context value null leads to several problems. One of these is that the system wants to use the same mapping for static resources twice. This is what the exception is about. I admit that the resulting error message could be improved... Another problem is that two application configurations could register the same servlet name twice. Having no contextName the system would not know which one to choose. But actually you would run in the same exception like the one below before... Think of an application like a webcontext of an webcontainer. Each application can have multiple servlets, brandings etc. but you can not mix them up. So the result is: If I have my RWT/RAP application with different EntryPoints, I have to register them with only a single ApplicationConfigurator? Okay, in such case, there should an error occur (maybe earlier) that tells me that I have two ApplicationConfigurators with the same contextName. *** Bug 372114 has been marked as a duplicate of this bug. *** |