The camel fhir component supports setting several query parameters. In the
implementation of FhirConfiguration all of these parameters are annotated with
@UriParam. Also in the implementation of FhirConfiguration I find the client
and clientFactory variables but they are annotated with @Metadata
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 paramete
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
Hey, all.
I have a route that's sitting on a port and it can receive 1 of 2 different XML
messages.
I was simply going to try to unmarshal with the first one, and if it errors,
unmarshal with the next one.
But is there a smarter or best practices way to handle this?
Thanks.
Hey,
I would use CBR
(https://www.enterpriseintegrationpatterns.com/patterns/messaging/ContentBasedRouter.html)
+ Body check for this.
Cheers
Dmitry
-Original Message-
From: Ron Cecchini [mailto:roncecch...@comcast.net]
Sent: Friday, June 21, 2019 2:23 PM
To: users@camel.apache.org
Su