[MAGNOLIA-3523] WebContextImpl is not Serializable Created: 20/Jan/11 Updated: 19/Dec/16 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
info.magnolia.context.WebContextImplTest#testSerializable verifies that WebContextImpl is serializable. While this is all good and well, it turns out that WebContextImpl is NOT serializable if it's been init()'d. And bang, the test fails: junit.framework.AssertionFailedError: WebContextImpl should be serializable, failed with: java.io.NotSerializableException: info.magnolia.context.RequestAttributeStrategy Since all WebContext instances are meant to be initialized before usage, we can conclude WebContextImpl is NOT serializable. Question is: does it need to be ? |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |