{"push_id":723777520,"size":1,"distinct_size":1,"ref":"refs/heads/POULPE-528_Jcommune_User_With_Id=0_not_found_error","head":"73f4cfe6d654058eb4d1f436728074f5a90d5da9","before":"ac08da004b83ff4ce9d0932c8b881b75fc535bc6","commits":[{"sha":"73f4cfe6d654058eb4d1f436728074f5a90d5da9","author":{"email":"7134c9e3670a37e0ef4d0664ac6699bd46abebd5@gmail.com","name":"Vladimir Kamensky"},"message":"Poulpe-528 Issue with 'User #0 not found' error\n\nWe have to customize serialization of the entity JCUser because of we used to loose 'id' and 'uuid' data from org.jtalks.common.model.entity.Entity class when saved other User details in session-storage-file.\nThe fix is similar to issue of PoulpeUser serialization (http://jira.jtalks.org/browse/POULPE-528)\n\nCreated:\n  - methods writeObject(), readObject() and serialVersionUID field.\n  - test method for checking is most fields of User entity serialized\n  - test method to assert the field `List<Group> groups` can't be serialized with rest of the JCUser fields.\n\nImplemented additional ObjectFactory method to reduce size of code in test method.","distinct":true,"url":"https://api.github.com/repos/jtalks-org/jcommune/commits/73f4cfe6d654058eb4d1f436728074f5a90d5da9"}]}