Is it possible to configure protocol buffers / protostuff to not generate the default empty constructor for a message?

Asked Feb 25 '20 at 14:34

Active Feb 25 '20 at 15:07

Viewed 332 times

I noticed that protocol buffers / protostuff generate the Java default no-argument constructor when there are required fields. Is there a way to instrument it to not do it for a specific message?

Example

message Response {
  required ErrorCode errorCode;
  repeated Data;
}

I would like it to generate only one constructor

public Response(ErrorCode errorCode) {};

edited Feb 25 '20 at 15:07

asked Feb 25 '20 at 14:34

Michele Dorigatti

How are you generating this protocol buffer? https://developers.google.com/protocol-buffers/docs/reference/java-generated doesn't say anything about constructors. – Andy Turner Feb 25 '20 at 14:46
I learned now that we use protostuff. – Michele Dorigatti Feb 25 '20 at 15:07
1

Is it a bean, or generated using code that generates beans? Because if so beans always require a zero argument constructor. So if that is the case, you might not be able to do that. – ggb667 Feb 25 '20 at 15:11
Not a bean, good point. – Michele Dorigatti Feb 25 '20 at 15:13

Is it possible to configure protocol buffers / protostuff to not generate the default empty constructor for a message?

Example

0 Answers0