oscerd commented on code in PR #21062:
URL: https://github.com/apache/camel/pull/21062#discussion_r2727476222
##########
components/camel-ocsf/src/generated/java/org/apache/camel/dataformat/ocsf/model/Account.java:
##########
@@ -0,0 +1,408 @@
+
+package org.apache.camel.dataformat.ocsf.model;
+
+import java.util.ArrayList;
+import java.util.LinkedHashMap;
+import java.util.List;
+import java.util.Map;
+import javax.annotation.processing.Generated;
+import com.fasterxml.jackson.annotation.JsonAnyGetter;
+import com.fasterxml.jackson.annotation.JsonAnySetter;
+import com.fasterxml.jackson.annotation.JsonIgnore;
+import com.fasterxml.jackson.annotation.JsonInclude;
+import com.fasterxml.jackson.annotation.JsonProperty;
+import com.fasterxml.jackson.annotation.JsonPropertyOrder;
+
+
+/**
+ * Account
+ * <p>
+ * The Account object.
+ *
+ */
+@JsonInclude(JsonInclude.Include.NON_NULL)
+@JsonPropertyOrder({
+ "name",
+ "type",
+ "uid",
+ "labels",
+ "tags",
+ "type_id"
+})
+@Generated("jsonschema2pojo")
Review Comment:
The schema is almost fixed and unless you change the underlined schema
through the python script (usually with a new ocsf schema release) the classes
will be like that for the time being, so I didn't really see the advantage of
placing them in target at build time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
