I can’t really give a definitive answer without seeing how the serializer/deserializer is implemented, but my initial suspicion is related to field name transformations.
GWT performs quite a bit of renaming and optimization during compilation, and domino-jackson works by mapping the original property string to the renamed field. Since the compiler renames the field consistently everywhere it’s used, the mapping still works. TeaVM, however, might be doing something different—possibly renaming fields inconsistently between the POJO and the classes that reference it. I’m not familiar enough with TeaVM’s internals to say for sure. The fact that explicitly specifying the property name in the annotation solves the issue makes the behavior even more puzzling without seeing the relevant code. On Tuesday, January 27, 2026 at 10:27:11 PM UTC+3 Tim Macpherson wrote: > > Works great for me in GWT so far, trying it in TeaVM now, so not sure if > this issue is in scope ? > TeaVM at the minimum does a bit of name changing and domino-jackson > deserializer fails with my DTO. One suggestion is add basic > Jackson annotations to every field in the DTO I think it's @JsonProperty, > then domino-jackson will adapt the deserializer. Anyone know if that's > correct ? Thanks > > Yahoo Mail: Search, Organize, Conquer > <https://mail.onelink.me/107872968?pid=nativeplacement&c=US_Acquisition_YMktg_315_SearchOrgConquer_EmailSignature&af_sub1=Acquisition&af_sub2=US_YMktg&af_sub3=&af_sub4=100002039&af_sub5=C01_Email_Static_&af_ios_store_cpp=0c38e4b0-a27e-40f9-a211-f4e2de32ab91&af_android_url=https://play.google.com/store/apps/details?id=com.yahoo.mobile.client.android.mail&listing=search_organize_conquer> > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/51a1ad21-3ed6-44a7-8cd2-c9040af91266n%40googlegroups.com.
