Answer below
2016-03-24 19:29 GMT+01:00 Zieris, Franz :
> Hi there,
> ...
>
> (2) The second problem still bugs me: Upon deserialization (from JSON back
> to
>
Java objects), GSON naturally needs to create instances for the
> non-primitive
> fields of the classes. In the case of Project
This also reminds me of a broken XStream converter for the IPath
objects. The result was a 4 MB big filelist packet for approx 1 files.
After some handmade optimization such a packet was 9 kb in size.
On 24.03.2016 23:56, Stefan Rossbach wrote:
It is still a bad design decision to serialize
It is still a bad design decision to serialize objects (that implement
an interface) where the interface contract does not state that the
implementation have to be serializable or not.
On 24.03.2016 23:37, Franz Zieris wrote:
> Awesome! The nested annotations look slightly weird, but I guss i
> Awesome! The nested annotations look slightly weird, but I guss it's not hard to get used to it.
>
> Any reason for not using the simpler @Signature(String,class, String.class)?
The @Argument annotation could also support additional properties, e.g. being one for being optional:
@Signature({@Argu
