| Summary: | Investigate RAP HttpService usage options | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Gunnar Wagenknecht <gunnar> |
| Component: | gyrex | Assignee: | Gunnar Wagenknecht <gunnar> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | andreas.mihm, mike.tschierschke |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 337100 | ||
| Bug Blocks: | 337635 | ||
|
Description
Gunnar Wagenknecht
I had a call with a RAP committer and it looks like there will be some progress. We likely won't get an official API but it might be possible to introduce an internal API that we can use. Long term, RAP needs some rework in order to support multiple instances within one OSGi framework instance. Setting Target Milestone to 1.0 in order to not loose track of important work for 1.0. We have preliminary support for this in RAP 1.4. Further work will happen in RAP 1.5. FWIW, I was able to remove the dependency on bug 241210 thanks to the new RAP Application API in RAP 1.5 M7. Victory on this one thanks to RAP 1.5 M7. No internal references anymore. |