Hi Ravi,

Thanks to have sent the mail ;)

for others: I asked Ravi to send this mail (he pinged on twitter) because
this can be a breaking change so not sure we want to directly impl it or
push it back to the spec. Any opinion welcomed.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le mer. 20 juin 2018 à 15:01, Ravisankar Challa <[email protected]> a
écrit :

> Hi Devs,
>
> I got something form here
> https://github.com/eclipse-ee4j/yasson/issues/23
>
> It Says
>
> Properties names specified in @jsonbpropertyorder annotation must be the
> original names of properties as it’s specified in Java class.
>
> as per yasson it should be
> @JsonbPropertyOrder({" lName", " fName"})
> class Person {
>     @JsonbProperty("last_name")
>     public String lName;
>     @JsonbProperty("first_name")
>     public String fName;
> }
>
> But Johnzon uses the renamed fields.
>
> as per spec it should be
> @JsonbPropertyOrder({" last_name", " first_name"})
> class Person {
>     @JsonbProperty("last_name")
>     public String lName;
>     @JsonbProperty("first_name")
>     public String fName;
> }
>
> Thanks,
> Ravi
>

Reply via email to