[
https://issues.apache.org/jira/browse/SLING-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080940#comment-14080940
]
Bertrand Delacretaz commented on SLING-3763:
--------------------------------------------
I have implemented your idea in a slightly simpler way in
http://svn.apache.org/r1614910 , by having the renderers implement
RendererFactory. That's not fantastic but requires less changes.
Can you check if that solves your issue? I don't see it in my environment
anyway, if you have a scenario or ideally an automated test that reproduces the
problem without this fix that would be great.
> 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)