JiriOndrusek commented on a change in pull request #2254:
URL: https://github.com/apache/camel-quarkus/pull/2254#discussion_r576782642



##########
File path: extensions/nitrite/runtime/src/main/doc/usage.adoc
##########
@@ -0,0 +1,12 @@
+If your persistence objects implement `java.io.Serializable`, you have to add 
configuration of all serializable classes.
+There is a new serialization support in GraalVM 21.0. Developers can configure 
classes
+for serialization via the serialization configuration file
+`-H:SerializationConfigurationResources=/path/to-serialization-config.json` 
option. For more
+information see https://github.com/oracle/graal/pull/2730[PR with feature].
+
+If your persistence objects implement `org.dizitart.no2.mapper.Mappable`. All 
classes have to
+implement also `java.io.Serializable` and have to be registered for 
serialization (see previous option),
+even though the Java serialization won't be used.
+
+
+

Review comment:
        fixed, thanks

##########
File path: 
integration-tests/nitrite/src/main/java/org/apache/camel/quarkus/component/nitrite/it/NitriteResource.java
##########
@@ -71,11 +73,17 @@ public Response getRepositoryClass() throws Exception {
     @POST
     @Consumes(MediaType.APPLICATION_JSON)
     @Produces(MediaType.APPLICATION_JSON)
-    public Object postRepositoryClass(Employee object) {
+    public Object postRepositoryClass(EmployeeSerializable object, 
@QueryParam("mappable") boolean mappable) {
+        String className = mappable ? EmployeeMappable.class.getName() : 
EmployeeSerializable.class.getName();
+        //if object, is mappable, construct it from serializable (it is 
conversion caused by tthe type in method parameter)

Review comment:
        fixed, thanks




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to