Serializing some other object in custom serializer

[nmorel]

Serializing some other object in custom serializer

[nmorel]

A possible workaround is to define an ObjectWriter for B inside your AJsonSerializer and to retrieve the underlying serializer.

public class AJsonSerializer extends JsonSerializer {

    static interface BJsonWriter extends ObjectWriter<B> {}

    private static final AJsonSerializer INSTANCE = new AJsonSerializer();

    private final JsonSerializer<B> bJsonSerializer;

    public static AJsonSerializer getInstance() {
        return INSTANCE;
    }

    private AJsonSerializer() {
        this.bJsonSerializer = (GWT.<AbstractObjectWriter>create( BJsonWriter.class )).getSerializer();
    }

    @Override
    protected void doSerialize( JsonWriter writer, A value, JsonSerializationContext ctx, JsonSerializerParameters params ) {
        writer.beginObject();
        writer.name( "b" );
        writer.value(bJsonSerializer.serialize( writer, value.getB(), ctx, params);
        writer.endObject();
    }
}

A bit more background about this issue : #40

I may add some factory interface where you could define all the serializer/deserializer you need.

[nmorel]

Can I ask why you need to define a custom serializer for your type A ?
You couldn't achieve it with annotations ?

[butlnor]

Wow thanks, that was what I was looking for. This works (except I had to use ObjectWriter<B> instead of JsonWriter<B>).

The reason for not using the annotations is, that the classes are in other older shared library projects, which must not have JSON annotations, as that projects are used elsewhere with custom build scripts, etc... So it's quite a requirement to leave the classes intact and not using additional dependencies.

I am very grateful, thanks.

[nmorel]

Ah right, fixed the example to use ObjectWriter. I didn't test it :p

You can use mixin annotation when you can't modify the class.

[butlnor]

The problem is that the classes don't have proper getters and setters (non-getter methods start with "get", but must not be called outside of their context, as they throw exceptions), but the fields are private or protected, so they cannot be serialized by the standard serializer. It's related to my previous issue.