Generated Java Classes as Serializable

[tarun4279]

We have used Netflix DGS Library & generated certain POJO classes from the graphQL schema

We used those classes in an internal model that needs to be cached and since the DGS generated classes are no serializable. We see failure in caching for that internal model.

Is it possible to make those generated classes serializable? May be setting certain properties under here

generateJava {
generateClient = true
packageName = "com.chegg.${mainPackageName}.generated"
}

Please share if this possible or not? Also, should this be considered as a feature?

[paulbakker]

By serializable, do you mean implement the Serializable interface? Since that’s such an outdated concept in Java, I don’t think it makes a lot of sense to add it.

…

On Wed, Jun 23, 2021 at 3:16 AM Tarun Kundhiya ***@***.***> wrote: We have used Netflix DGS Library & generated certain POJO classes from the graphQL schema We used those classes in an internal model that needs to be cached and since the DGS generated classes are no serializable. We see failure in caching for that internal model. Is it possible to make those generated classes serializable? May be setting certain properties under here generateJava { generateClient = true packageName = "com.chegg.${mainPackageName}.generated" } Please share if this possible or not? Also, should this be considered as a feature? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#430>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA2XLBAQPDZGD66YDYCMUTTUGX6NANCNFSM47FPOS6A> .

[StringKe]

Some rpc serialization protocols require the use of Serializable Is there any other way to support automatic implementation of Serializable at the moment?

[paulbakker]

Serializable is a really outdated concept, I don’t think the generated code should support it.

…

On Fri, Sep 15, 2023 at 8:58 PM 青木 ***@***.***> wrote: Some rpc serialization protocols require the use of Serializable Is there any other way to support automatic implementation of Serializable at the moment? — Reply to this email directly, view it on GitHub <#430 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA2XLCBL4KW7OW76MXL2H3X2UPVPANCNFSM47FPOS6A> . You are receiving this because you commented.Message ID: ***@***.***>

[ivanp]

It's old, yes. But like StringKe mentions it is required by many modules, such as Spring Cache default serializer.