Pop quiz. Why is the following Java 8 code unsafe? UPDATE: this code is fine, see comments. Still good to think about, though.<\/p>\n
To provide some\u00c2\u00a0context, Here\u00e2\u20ac\u2122s the function signature of that Ah, yes, Spring, which because of the I\u00e2\u20ac\u2122m having trouble coming to terms with what seems like a gaping hole. Do you agree with this analysis? If so, how do you deal with it? Immutable object classes seem like an obvious choice, but will introduce lots of overhead in other parts of the code that need to manipulate the entities. A builder pattern gets awkward and verbose quickly, as it hoists all that complexity on to the caller.<\/p>\n How do you handle situations like this? I\u00e2\u20ac\u2122d love to hear it.<\/p>\n If you produce libraries, please include documentation on what is and isn\u00e2\u20ac\u2122t guaranteed w.r.t. async calls. -m<\/p>\n","protected":false},"excerpt":{"rendered":" Pop quiz. Why is the following Java 8 code unsafe? UPDATE: this code is fine, see comments. Still good to think about, though. Entity e = new Entity(); e.setName(“my new entity”); persistanceLayer.put(e); To provide some\u00c2\u00a0context, Entity is a POJO representing something we want to store in a database. And persistanceLayer is an instance of a…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[27,22],"tags":[],"class_list":["post-1158","post","type-post","status-publish","format-standard","hentry","category-languages","category-software"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tEntity e = new Entity();
\ne.setName(\"my new entity\");
\npersistanceLayer.put(e);
\n<\/code><\/p>\nEntity<\/code> is a POJO<\/abbr> representing something we want to store in a database. And persistanceLayer<\/code> is an instance of a Data Access Object responsible for storing the object in the database. Don\u00e2\u20ac\u2122t see it yet?<\/p>\nput<\/code> method<\/p>\n@Async
\n<E extends AbstractEntity> CompletableFuture<E> put(E newEntity);
\n<\/code><\/p>\n@Async<\/code><\/a> annotation will proxy this method and cause it to execute in a different thread. The object getting passed in is clearly mutable, and by my reading of the Java Memory Model<\/a>, there\u00e2\u20ac\u2122s no guarantee that the other thread\u00e2\u20ac\u2122s view of the update that happened in the setName<\/code> method will be visible. In other words, there\u00e2\u20ac\u2122s no guarantee the two threads idea of \u00e2\u20ac\u0153before-ness\u00e2\u20ac\u009d will be the same; who knows what might have been reordered or cached?<\/p>\n