![]() Jakarta EE 9.1 is still not even JDK 9 compatible which is a huge hammer in a lot of people plans, and are so far away from being 11 compatible, that 16 or 17 right now for them seems out of reach for at least 2 years. Version 3.0 is under way with Jakarta specific releases for anything I've found on that front, and once finalized will port across. This library would have the largest impact from forcing modularizaiton Kotlin so-far does not seem to be adopting JDK 9 and up, and are following the JDK 8 pathway, going non-modular (even on higher jdk's making a move to JDK 11 very hard, JDK 17 is completely impossible for them with the block). ![]() to find by property only removes all invalid encapsulation requests As value objects though, these don't bring back the final result, only whats necessary to calculate the final result -> LocalDateTime/OffsetDateTime best example hereġ,a) Our final result ended up in us simply registering a serializer and deserializer for each of the value objects in the JDK, and handling it properly by property, getters and settersġ.b) The list of value objects in JDK is not exhaustive, setting all objects found in package java. This issue is only specific to referencing JDK Internal Value Objects, you must use Property fetch and Set. The problem is closer to usage, than implementation though, through devious attempts of resolution -įield Accessors to JDK Internals is banned across the board, this is correct according to the principle of encapsulation. ![]() ![]() This is something that I am specifically looking at. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |