@DirtiesContext for GemFire integration tests
Applies @DirtiesContext to all Spring Session Data GemFire integration tests to ensure that no lingering GemFire (peer or client) cache instances cause conflicts on downstream tests. Fixes gh-396
This commit is contained in:
@@ -19,7 +19,8 @@
|
||||
<gfe:cache properties-ref="gemfireProperties" close="true"/>
|
||||
|
||||
<bean class="org.springframework.session.data.gemfire.config.annotation.web.http.GemFireHttpSessionConfiguration"
|
||||
p:indexableSessionAttributes="one, two, three" p:maxInactiveIntervalInSeconds="3600" p:springSessionGemFireRegionName="Example"
|
||||
p:serverRegionShortcut="#{T(com.gemstone.gemfire.cache.RegionShortcut).LOCAL}"/>
|
||||
p:indexableSessionAttributes="one, two, three" p:maxInactiveIntervalInSeconds="3600"
|
||||
p:serverRegionShortcut="#{T(com.gemstone.gemfire.cache.RegionShortcut).LOCAL}"
|
||||
p:springSessionGemFireRegionName="XmlExample"/>
|
||||
|
||||
</beans>
|
||||
|
||||
Reference in New Issue
Block a user