XStream
  1. XStream
  2. XSTR-286

XStream should provide helpful exception if serializing itself

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2
    • Component/s: None
    • Labels:
      None

      Description

      Currently XStream cannot serialize itself as it's internal state is changing whilst serialization occurs (see XSTR-50).

      When this happens a ConcurrentModificationException is thrown but it is not clear why to users. I would like XStream to detect if itself is being serialized (or any of its internal classes such as mappers) and throw an easy to understand exception (such as XStreamCannotSerializeItselfException).

      Note, it should be possible for XStream to serialize other instances of other XStreams.

        Issue Links

          Activity

          Hide
          Jörg Schaible added a comment -

          well, in the end it should be able to serialize itself ...

          Show
          Jörg Schaible added a comment - well, in the end it should be able to serialize itself ...
          Hide
          Jörg Schaible added a comment -

          XStream throws now a ConversionException with an appropriate message.

          Show
          Jörg Schaible added a comment - XStream throws now a ConversionException with an appropriate message.
          Hide
          Guilherme Silveira added a comment -

          moving to 1.2

          Show
          Guilherme Silveira added a comment - moving to 1.2

            People

            • Assignee:
              Unassigned
              Reporter:
              Joe Walnes
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: