Hi
Yeah we can make it possible to plugin a custom client. However then you
need setup all of this yourself for authentication, proxy and so on
https://issues.apache.org/jira/browse/CAMEL-22370
On Sat, Aug 23, 2025 at 5:57 PM Chirag
wrote:
> Hello Claus,
>
> While camel-graphql
Hello Claus,
While camel-graphql component doesn't document this
https://camel.apache.org/components/4.10.x/graphql-component.html,
underlying class has following:
https://github.com/apache/camel/blob/main/components/camel-graphql/src/main/java/org/apache/camel/component/gr
es("application/json")
>>> .to("direct:swapi-graphql-all-films2");
>>> from("direct:swapi-graphql-all-films2")
>>> .setBody(constant("{ allFilms { films { title director releaseDate } }
>>> }"))
>>> .to("graph
cation/json")
>> .to("direct:swapi-graphql-all-films2");
>> from("direct:swapi-graphql-all-films2")
>> .setBody(constant("{ allFilms { films { title director releaseDate } }
>> }"))
>> .to("graphql://https://swapi-graphql.netli
wapi-graphql-all-films2")
> .setBody(constant("{ allFilms { films { title director releaseDate } } }"))
> .to("graphql://https://swapi-graphql.netlify.app/.netlify/functions/index
> ")
> .convertBodyTo(String.class);
> The reason for the failure is inter
ot;graphql://https://swapi-graphql.netlify.app/.netlify/functions/index";)
.convertBodyTo(String.class);
The reason for the failure is interesting:
1. GraphQL component constructs POST and invokes HTTP
2. netlify's index URL returns 301 with /graphql - and that forces POST to
be changed to
ssed to the redirected URL.
>
> what will be better way to handle it ? Should such scenario be handled by
> passing a custom http client that disables redirect and capture error?
>
> If GraphQL component was built using camel-http underneath - it could
> return many more values to make some decisions after exchange is called .
>
--
Claus Ibsen
Apache Common HTTP Client - and as GET - which is where the "query" is
not passed to the redirected URL.
what will be better way to handle it ? Should such scenario be handled by
passing a custom http client that disables redirect and capture error?
If GraphQL component was built usin
point uri, then you should use *toD* and
> not *to*. To D is for To Dynamic.
>
> On Sun, Jan 24, 2021 at 9:05 AM David Holiday
> wrote:
> >
> > Hello fellow Camel riders,
> >
> > I'm trying to use the graphql component to do some integration work with
&g
Hi
For dynamic queries in the endpoint uri, then you should use *toD* and
not *to*. To D is for To Dynamic.
On Sun, Jan 24, 2021 at 9:05 AM David Holiday wrote:
>
> Hello fellow Camel riders,
>
> I'm trying to use the graphql component to do some integration work with
> Git
Hello fellow Camel riders,
I'm trying to use the graphql component to do some integration work with
Github and I've noticed some odd behaviors:
1) for some reason, I can't use Simple to dynamically create queries. When
I log the query it shows up correctly. for example:
the Ja
11 matches
Mail list logo
