Hi Geoff, Geoff Groos wrote:
> Hey guys, > > We’re just about to go to version 1.0, so I’m running over every piece of > tech-debt I can think of to make sure all my ducks are in a row, and I > found this in our project file (an XML serialized model): > > <ProjectState.ImmutableMomento> > <associatedRunId>b723fec2-50f9-45fa-9a41- fee8d022b544</associatedRunId> > <!-- ... --> > </ProjectState.ImmutableMomento> > <ProjectState.ImmutableMomento> > <associatedRunId > reference="../../ProjectState.ImmutableMomento/associatedRunId"/> > > I cant think of a good reason for a UUID not to be immutable by default. > Doing oneID == anotherID has to be as taboo as aString == anotherString to > anybody whose willing to use a UUID object, meaning I don't think there’s > any reason to preserve reference equality in serialization. You're absolutely right. Can you open a JIRA ticket to track the issue, please? Simply follow instructions at http://xstream.codehaus.org/issues.html Cheers, Jörg Sad to say, but 2 hours earlier, and it would already have been part of the new release :-/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
