| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ic77338304dc7e58e49f27dcdaf0bab2e00f5bba6
|
|
|
|
| |
Change-Id: I99ea86d8842324884dda3a5c392f37e8d4a7acf6
|
|
|
|
| |
Change-Id: Icf82377b0d47166d59e8be5f2f8b450d654302d7
|
|
|
|
| |
Change-Id: I9ec103a1a42d8888d6f680f477393807223740cf
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue is fixed by changing the normal HashMap inside the inheritable
thread local to a map implementation holding only weak references to the
values (WeakValueMap).
Also included is a test UI that starts threads, which run until the JVM
is quit. This along with VisualVM was used to reproduce the issue and
verify the fix.
Change-Id: I116cc4e56e8a19c3b770abab6b18b9e262f4dafa
|
|
|
|
| |
Change-Id: Ic7389a06726026383b96de80b0d038ed11e9d273
|
|
|
|
| |
Change-Id: I7ca62c5706fd37e7c44ed46703bcdce159b367f4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement VaadinPortlet.getCurrent() to use VaadinService.getCurrent()
instead of having a separate thread local variable. This is done to
avoid classloading issues when determining which instances to preserve
in CurrentInstance.setThreadLocals. The two current instances have
previously been kept in sync in all cases except during
VaadinPortlet.init where VaadinService has not yet been created.
VaadinPortlet.setCurrent() is removed as no way of preserving its
semantics has been found. This breaks API compatibility, but is probably
better than having a deprecated implementation that can not work as
expected in all situations.
The same changes have also been made to VaadinServlet to maintain the
symmetry.
Change-Id: I0a1ccc07a4aeecec558a9aaae211bd56207313d8
|
|
|
|
| |
Change-Id: I2b3f83220070f1f46730d956abb24ba9edf02f20
|
|
|
|
| |
Change-Id: If31a965f925ca2bedb25c712b83ccb070a9e71a0
|
|
|
|
| |
Change-Id: I40a59087fea7fbd4ad202ef803b42bbc76bf94d3
|
|
|
|
| |
Change-Id: I419ce4581d1a8b84d4236a85a1333d23f3423b2e
|
|
|