[
https://issues.apache.org/jira/browse/SLING-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080918#comment-14080918
]
Bertrand Delacretaz commented on SLING-3763:
--------------------------------------------
Thanks for your patch - it looks like the Renderer service design is broken, it
doesn't lead to stateless services.
Your patch would work but it's bit complicated IMO, I'll look for a simpler
solution to work around this broken API.
For now, I have added checks in http://svn.apache.org/r1614898 to make sure the
renderers are not used by multiple threads at a given time.
> Sling Junit Renderer Service Factory
> ------------------------------------
>
> Key: SLING-3763
> URL: https://issues.apache.org/jira/browse/SLING-3763
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Michael Tarantino
> Attachments: SlingJunitRendererFactory.patch
>
>
> In the current version of Sling JUnit, the renderer service is shared between
> requests. In case of parallel request the output is mixed between the
> different requests.
> To fix this issue, we([~frm] and I) create Renderer Factories which provide a
> single renderer object for each request.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
