Subclass in a field with a concrete type is written, and then dropped on read

Abierto
  • ¿Algo no está bien?
#4,168 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@GarvSaxena ya está trabajando en esto.

Desde el 16/10/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
backend

Línea de trabajo

Start with the Java JSON serialization and deserialization paths exercised by the provided ForyJson example, then compare their handling of a concrete declared field whose runtime value is a subclass with the binary module’s behavior. Reproduce the example and trace how the JSON reader chooses the field type. Done means it either preserves the subclass and its breed field or reports clearly that writing would discard subclass data.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Search before asking
  • I had searched in the issues and found no similar issues.
Version

1.7.7

Component(s)

Java

Minimal reproduce step

A field has a declared type. The declared type is a concrete class, and the class is not final. The value is an instance of a subclass.

Version 1.7.7 writes the fields of the subclass, which 1.7.6 did not. The read operation still builds the declared type and ignores those fields. The data is therefore in the document, and nothing can read it. Fory gives no error at either step.

import org.apache.fory.Fory;
import org.apache.fory.config.Language;
import org.apache.fory.json.ForyJson;

public class SubclassStateDropped {

    public static class Animal {
        String name = "generic";
        public String toString() { return "Animal(name=" + name + ")"; }
    }

    public static class Dog extends Animal {
        String breed = "lab";
        public Dog() { name = "rex"; }
        public String toString() { return "Dog(name=" + name + ", breed=" + breed + ")"; }
    }

    public static class Owner {
        private Animal pet = new Dog();
        public Owner() { }
        public String toString() { return "Owner(pet=" + pet + ")"; }
    }

    public static void main(String[] args) {
        Owner original = new Owner();

        ForyJson json = ForyJson.builder().withFieldMode(true).build();
        byte[] doc = json.toJsonBytes(original);
        System.out.println("fory-json wrote : " + new String(doc));
        System.out.println("fory-json read  : " + json.fromJson(doc, Owner.class));

        Fory core = Fory.builder().withLanguage(Language.JAVA).requireClassRegistration(false).build();
        System.out.println("fory-core read  : " + core.deserialize(core.serialize(original)));
    }
}
What did you expect to see?

One of two results.

In the first result, fory-json reads the document it wrote and gives Owner(pet=Dog(name=rex, breed=lab)). The binary module gives this result for the same object, as the third line of the output shows, so it is the behaviour the project has already established.

In the second result, fory-json refuses the write operation. The error message tells the user that the runtime type is a subtype of the declared type, and that a write operation discards data.

Fory JSON has no open polymorphism, and we know that this is a design decision. That makes the second result the one we expected. In both results the application can find that Fory made a decision.

What did you see instead?

Owner(pet=Animal(name=rex)), and no error from either step.

The document holds "breed":"lab". The value of name is "rex", which the constructor of Dog assigns, so the object written was the Dog. The read operation builds an Animal and ignores breed. No part of the API tells the application that the field was discarded.

Anything Else?

No response

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Lenguaje dominante
Java
Estrellas
4.6k
Forks
470
Merge medio
9 h 28 min
PR fusionados (30 d)
33

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/fory

Todos los issues de apache/fory

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.