GitHub user svenmeier opened a pull request:
https://github.com/apache/wicket/pull/214
experimenting with suspension of requestCycle via servlet 3 async
Notes:
- enabled async-supported in web.xml for ComponentReferenceApplication
- LinkPage shows usage of RequestCycle#suspend()
- pageAccessSynchronizer uses the requestCycle instead of the thread
now, since two threads might process a page (PageAccessSynchronizerTest
still fails)
- ServletWebRequest must not call httpServletRequest#getContextPath(),
since it returns null during async processing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/wicket suspend_request_cycle
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/wicket/pull/214.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #214
----
commit 64f746fba8bb0235dd870e2a9d2ba1eaa192ada5
Author: Sven Meier <[email protected]>
Date: 2017-02-17T17:30:51Z
experimenting with suspension of requestCycle via servlet 3 async
Notes:
- enabled async-supported in web.xml for ComponentReferenceApplication
- LinkPage shows usage of RequestCycle#suspend()
- pageAccessSynchronizer uses the requestCycle instead of the thread
now, since two threads might process a page (PageAccessSynchronizerTest
still fails)
- ServletWebRequest must not call httpServletRequest#getContextPath(),
since it returns null during async processing
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
