Timeline for Initialize service in pipeline to be available through one httprequest
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2018 at 18:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 11, 2018 at 18:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 11, 2018 at 17:29 | answer | added | Kam Figy | timeline score: 2 | |
| Jun 24, 2018 at 18:09 | comment | added | Erik J. | @JasonBooth we never resolved this. We are in the middle of upgrading to 9.0 so perhaps we'll see some change there. For now we worked around it by building a singleton (static) class with lazy initializers. Not the perfect solution, but it works. | |
| Jun 19, 2018 at 22:04 | history | edited | Mark Cassidy♦ |
edited tags
|
|
| Jun 19, 2018 at 21:54 | comment | added | Jason Booth | We ran into this exact issue today on Sitecore 8.2 Update 6. Our solution was to use the Service Locator anti-pattern in the processor to get our service. This properly instantiated it once for the life of the request, across the container. Has to be a Sitecore bug... | |
| Jun 19, 2018 at 20:50 | comment | added | Jason Booth | did you ever resolve this? I am seeing the same behavior and am stumped... | |
| S Mar 28, 2018 at 9:26 | history | suggested | Bartłomiej Mucha | CC BY-SA 3.0 |
formatting
|
| Mar 28, 2018 at 7:26 | review | Suggested edits | |||
| S Mar 28, 2018 at 9:26 | |||||
| Mar 28, 2018 at 7:07 | review | First posts | |||
| Mar 28, 2018 at 7:25 | |||||
| Mar 28, 2018 at 7:02 | history | asked | Erik J. | CC BY-SA 3.0 |