JiriOndrusek commented on code in PR #7939:
URL: https://github.com/apache/camel-quarkus/pull/7939#discussion_r2513284591


##########
extensions/xchange/deployment/src/main/java/org/apache/camel/quarkus/component/xchange/deployment/XchangeProcessor.java:
##########
@@ -138,7 +138,7 @@ void 
registerProxyClasses(BuildProducer<NativeImageProxyDefinitionBuildItem> nat
 
     @BuildStep
     void 
runtimeInitializedClasses(BuildProducer<RuntimeInitializedClassBuildItem> 
runtimeInitializedClasses) {
-        Stream.of(Order.class.getName())
+        Stream.of(Order.class.getName(), 
"org.apache.http.impl.auth.NTLMEngineImpl")

Review Comment:
   without the registration, there is an error:
   ```
   Error: Detected an instance of Random/SplittableRandom class in the image 
heap. Instances created during image generation have cached seed values and 
don't behave as expected. If these objects should not be stored in the image 
heap, you can use 
   
       '--trace-object-instantiation=java.security.SecureRandom'
   
   to find classes that instantiate these objects. Once you found such a class, 
you can mark it explicitly for run time initialization with 
   
       '--initialize-at-run-time=<culprit>'
   
   to prevent the instantiation of the object.
   The object was probably created by a class initializer and is reachable from 
a static field. You can request class initialization at image runtime by using 
the option --initialize-at-run-time=<class-name>. Or you can write your own 
initialization methods and call them explicitly from your main entry point.
   Detailed message:
   Trace: Object was reached by
     trying to constant fold static field 
org.apache.http.impl.auth.NTLMEngineImpl.RND_GEN
       at org.apache.http.impl.auth.NTLMEn
       ```



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

Reply via email to