You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (Jira)" <ji...@apache.org> on 2020/02/27 08:37:00 UTC
[jira] [Updated] (CAMEL-14619) Introduce a SPI to auntomatic bind
data format to transports
[ https://issues.apache.org/jira/browse/CAMEL-14619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luca Burgazzoli updated CAMEL-14619:
------------------------------------
Description:
Some data formats such as the future CloudEvent one (https://issues.apache.org/jira/browse/CAMEL-13335) have specifications that describe how to bind them to specific transports (https://github.com/cloudevents/spec) so we should introduce a SPI to make this binding automatic so in a route like:
{code:java}
from("undertow://http://0.0.0.0:8080")
.unmarshal().cloudEvents()
.to("kafka:my-topic");
{code}
the exchange gets automatically translated to a Kafka message according to the CloudEvent binding specs for Kafka.
was:
Some data formats such as the future CloudEvent one (https://issues.apache.org/jira/browse/CAMEL-13335) have specifications that describe how to bind them to specific transports (https://github.com/cloudevents/spec) so we should introduce a SPI to make this binding automatic so in a route like:
{code:java}
from("undertow://http://0.0.0.0:8080")
.unmarshal().cloudEvents()
.to("kafka:my-topic");
{code}
the exchange gets automatically translated to a kafka message according to the CloudEvent binding specs.
> Introduce a SPI to auntomatic bind data format to transports
> ------------------------------------------------------------
>
> Key: CAMEL-14619
> URL: https://issues.apache.org/jira/browse/CAMEL-14619
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-api
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Minor
> Fix For: 3.x
>
>
> Some data formats such as the future CloudEvent one (https://issues.apache.org/jira/browse/CAMEL-13335) have specifications that describe how to bind them to specific transports (https://github.com/cloudevents/spec) so we should introduce a SPI to make this binding automatic so in a route like:
> {code:java}
> from("undertow://http://0.0.0.0:8080")
> .unmarshal().cloudEvents()
> .to("kafka:my-topic");
> {code}
> the exchange gets automatically translated to a Kafka message according to the CloudEvent binding specs for Kafka.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)