Thanks John, you were right. We were simply looking at the configuration object
too early. Thanks for your help.
-Original Message-
From: John Poth
Sent: 27. juni 2019 18:02
To: users@camel.apache.org
Subject: Re: How to set client or clientFactory in the FhirConfiguration object?
Hi
Hi Stig,
Endpoint options are set at a later stage[1] which is why you don't see the
desired cutstom client.
You could also set a breakpoint at [2] to see which client is really used
for the update method. From what I see you're setting it up correctly.
HTH,
John.
[1]
Hi John,
I work with Paw. We're trying to set either the client or client factory via
the URI header, because we'd like to add a request interceptor to the client.
We would like to log error response bodies.
You are right that it was weird to use HTTP_QUERY. Instead we've done the
following:
Hi Paw, I'm not sure why you're trying to set the custom IGenericClient
through the Camel header; I'd need more info on your requirements. If you
can link to a github project or whatnot that'd be great.
As stated, you can set the custom client in your route URI directly [1]
referencing your bean
I still have problem setting my custom client in the FhirConfiguration. I have
implemented a custom client TestClient implementing the IGenericClient
interface and I annotated the class with @Component. I also implemented a route
where I try to set my custom client using the following strategy
Sure you can check [1] for and example, thanks!
[1]
https://github.com/apache/camel/blob/b9a3117f19dd19abd2ea8b789c42c3e86fe4c488/components/camel-fhir/camel-fhir-component/src/test/java/org/apache/camel/component/fhir/FhirCustomClientConfigurationIT.java#L63
On Tue, Jun 25, 2019 at 7:42 AM
Hi
I have fixed this for master, eg Camel 3
On Fri, Jun 21, 2019 at 2:20 PM Claus Ibsen wrote:
>
> And btw you should still be able to configure them as query
> parameters, as those @UriParam etc are for documentation purposes.
>
> On Fri, Jun 21, 2019 at 2:19 PM Claus Ibsen wrote:
> >
> > Hi
And btw you should still be able to configure them as query
parameters, as those @UriParam etc are for documentation purposes.
On Fri, Jun 21, 2019 at 2:19 PM Claus Ibsen wrote:
>
> Hi
>
> Ah those 2 are wrong they should be @UriParam also. You are welcome to
> log a JIRA and provide a PR
>
> On
Hi
Ah those 2 are wrong they should be @UriParam also. You are welcome to
log a JIRA and provide a PR
On Fri, Jun 21, 2019 at 10:10 AM Paw B Sørensen
wrote:
>
> The camel fhir component supports setting several query parameters. In the
> implementation of FhirConfiguration all of these
