The problem with cache invalidation for muttable objects in a multithreaded environment isn't straightforward .. I'll get back to you on the exception scenario...
- toString shouldn't change the object's state Vincent
- RE: toString shouldn't change the object's state Jerome Louvel
- Re: toString shouldn't change the object's state Vincent
- Re: toString shouldn't change the object's s... Piyush Purang
- Re: toString shouldn't change the object... Vincent
- Re: Re: toString shouldn't change t... John D. Mitchell
- Re: Re: toString shouldn't chan... Piyush Purang
- Re: toString shouldn't chan... Vincent
- RE: toString shouldn't chan... Jerome Louvel
- Re: toString shouldn't chan... Vincent
- RE: toString shouldn't chan... Jerome Louvel

