-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Serialization] Hazelcast extension : using HazelcastSedaProducer with transferExchange=true #2101
Comments
Support for JDK serialization/deserialization oracle/graal#2730 was merged recently and should be delivered with GraalVM 21.0.0 |
I'll add the integration test when we move to GraalVm 21.0.0 |
Also add integration test for Query on Map, using a Serializable object. |
@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 |
The 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 |
Blocked by quarkusio/quarkus#15380 |
@davsclaus Maybe you should comment on this issue : https://issues.apache.org/jira/browse/CAMEL-16805. I'm not sure if I understood everything. Should we build something new, or should we change the |
OK added a comment in JIRA. |
I think for now we should just NOT support transferExchange in the camel-hazelcast-extension. Then that can be revisted later when CAMEL-16805 is implemented. |
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. It's related to this issue graal#460
Also for integration tests for HazelcastAggregationRepository and ReplicatedHazelcastAggregationRepository, that use the same Serializable class object.
The text was updated successfully, but these errors were encountered: