| Summary: | LifeCycleAdapterFactory violates scope of ApplicationContext | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Rüdiger Herrmann <ruediger.herrmann> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | fr.appel | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 1.4 RC1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 337787, 341761 | ||||||
| Attachments: |
|
||||||
|
Description
Rüdiger Herrmann
... I am working on a patch - the test case is with what I am currently struggling (create a new session within the test) Created attachment 192729 [details]
Partial fix
The patch converts the static fields to member fields and thus solves the problem that LifeCycleAdapterFactory may mix adapters from different RWTContexts.
Hovever, it introduces a new problem: as adapter factories have session scope, now each session has its own set of LifeCycleAdapter (LifeCycleAdapter_Test#testXXXFromDifferentSessions fail)
A possible solution to this problem would be to let the LifeCycleAdapterFactory use a a per-RWTContext buffer to store already known lifecycle adapters.
My current thinking is to let the AdapterFactory have application scope (i.e. make AdapterManagerImpl application scoped). See bug 342302. Resolved with closing bug 342302. |