[MGNLEESOLR-69] Stop using non serialisable objects in FacetedSolrSearchProvider Created: 09/Jul/15  Updated: 15/Apr/16  Resolved: 30/Jul/15

Status: Closed
Project: Solr Search Provider
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0

Type: Bug Priority: Critical
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: backlog541
Remaining Estimate: 0d
Time Spent: 1d 4.1h
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2015-06-01 at 17.23.05.png    
Issue Links:
causality
is causing MGNLEESOLR-76 Do not handle differently with search... Closed
relation
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:
Sprint: Sprint 3 (Kromeriz)
Story Points: 8

 Description   

Fields in a Serializable class must themselves be either Serializable or transient even if the class is never explicitly serialized or deserialized. That's because under load, most J2EE application frameworks flush objects to disk, and an allegedly Serializable object with non-transient, non-serializable data members could cause program crashes, and open the door to attackers.


Generated at Mon Feb 12 10:59:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.