Log Message
Update documentation with solution possibilities for concurrency problems using auto-detection for annotations.
Modified Paths
Diff
Modified: trunk/xstream-distribution/src/content/annotations-tutorial.html (2104 => 2105)
--- trunk/xstream-distribution/src/content/annotations-tutorial.html 2013-08-27 06:53:56 UTC (rev 2104)
+++ trunk/xstream-distribution/src/content/annotations-tutorial.html 2013-08-27 07:17:46 UTC (rev 2105)
@@ -507,7 +507,9 @@
unmarshalling. Unfortunately an annotation is defining a change in configuration that is now applied while object
marshalling is processed. Therefore will the auto-detection mode turn XStream's marshalling process in a thread-unsafe
operation. While XStream synchronizes the configuration modification, it cannot guard concurrent reads and you may run
-under certain circumstances into concurrency problems.</p></li>
+under certain circumstances into concurrency problems. If you abolutely have to rely on annotation processing on the
+fly, you will have to use separate XStream instances for each thread - either by using everytime a new instance or by a
+shared pool.</p></li>
<li><strong>Exceptions</strong>
<p>XStream uses a well-defined exception hierarchy. Normally an InitializationException is only thrown while XStream
is configured. If annotations are processed on the fly they can be thrown obviously also in a marshalling process.</p></li>
Modified: trunk/xstream-distribution/src/content/faq.html (2104 => 2105)
--- trunk/xstream-distribution/src/content/faq.html 2013-08-27 06:53:56 UTC (rev 2104)
+++ trunk/xstream-distribution/src/content/faq.html 2013-08-27 07:17:46 UTC (rev 2105)
@@ -634,7 +634,8 @@
allowing objects to be serialized/deserialized concurrently (unless you enable the
<a href="" to process annotations on-the-fly). Actually the
creation and initialization of XStream is quite expensive, therefore it is recommended to keep the XStream instance
- itself.</p>
+ itself. If you abolutely have to rely on annotation processing on the fly, you will have to use separate XStream
+ instances for each thread - either by using everytime a new instance or by a shared pool.</p>
<!-- ...................................................... -->
<h2 id="Scalability_Memory">How much memory does XStream consume?</h2>
To unsubscribe from this list please visit:
