[GitHub] [camel-quarkus] zbendhiba opened a new issue #2101: Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] zbendhiba opened a new issue #2101: Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

GitBox

zbendhiba opened a new issue #2101:
URL: https://github.com/apache/camel-quarkus/issues/2101


   On native mode, it's impossible use to write HazelcastSedaProducer with transferExchange=true.
   The reason is there an issue while writing object of type [DefaultExchangeHolder](https://github.com/apache/camel/blob/master/core/camel-support/src/main/java/org/apache/camel/support/DefaultExchangeHolder.java). It's related to this issue [graal#460](https://github.com/oracle/graal/issues/460)


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #2101: [GraalVM 21.0.0] Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

GitBox

ppalaga commented on issue #2101:
URL: https://github.com/apache/camel-quarkus/issues/2101#issuecomment-754114944


   Support for JDK serialization/deserialization https://github.com/oracle/graal/pull/2730 was merged recently and should be delivered with GraalVM 21.0.0
   


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] zbendhiba commented on issue #2101: [GraalVM 21.0.0] Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

GitBox
In reply to this post by GitBox

zbendhiba commented on issue #2101:
URL: https://github.com/apache/camel-quarkus/issues/2101#issuecomment-754756202


   I'll add the integration test when we move to GraalVm 21.0.0


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] zbendhiba commented on issue #2101: [GraalVM 21.0.0] Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

GitBox
In reply to this post by GitBox

zbendhiba commented on issue #2101:
URL: https://github.com/apache/camel-quarkus/issues/2101#issuecomment-755174538


   + integration test for Query on Map, using a Serializable object.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] zbendhiba edited a comment on issue #2101: [GraalVM 21.0.0] Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

GitBox
In reply to this post by GitBox

zbendhiba edited a comment on issue #2101:
URL: https://github.com/apache/camel-quarkus/issues/2101#issuecomment-755174538


   Also add integration test for Query on Map, using a Serializable object.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #2101: [GraalVM 21.0.0] Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

GitBox
In reply to this post by GitBox

lburgazzoli commented on issue #2101:
URL: https://github.com/apache/camel-quarkus/issues/2101#issuecomment-758073691


   @davsclaus I wonder if we should start a stream to investigate a  pluggable strategy for this and other similar cases i.e. allowing to use json, protobuf & what not


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] davsclaus commented on issue #2101: [GraalVM 21.0.0] Hazelcast extension : using HazelcastSedaProducer with transferExchange=true

GitBox
In reply to this post by GitBox

davsclaus commented on issue #2101:
URL: https://github.com/apache/camel-quarkus/issues/2101#issuecomment-759451482


   The `transferExchange` is a bad design as it enforces to use Camel on both sides, and gives the impression that you can transfer the current state of the exchange to some cache / storage, and then retrieve it later, and then _continue_ routing it.
   
   Its for historical use we had it, and when Java objects wasn't yet a big big security vulnerability and warning.
   
   Instead what is a more general concept would be to have an API for serializing / de-serializing a Camel message with its body and header (eg user payload) and not to include internal exchange state that may be stored as exchange properties and whatnot.
   
   Such a API / contract can also be used by EIPs and components to store user payload more easily. And then we can have implementations for common types, such as you refer to with json/xml payloads. And for binary then avro/protobuf/what not
   
   
   


----------------------------------------------------------------
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:
[hidden email]