[CAMEL-17337] camel-fhir - FhirComponent regression between 2.2x and 3.x releases

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.x
• Fix Version/s: 3.15.0
• Component/s: camel-fhir
• Estimated Complexity: Unknown
• Regression: Regression
• Assignee: Unassigned
• Reporter: Paul Coombes
• Created: 14/Dec/21 16:58
• Updated: 16/Dec/21 06:27
• Resolved: 16/Dec/21 06:27

Description

In the 3.x branches, the FhirComponent contains a FhirConfiguration property which results in the getClient method creating a new IGenericClient from the method supplied configuration due to the configuration property never being initialised.

@Component("fhir")
public class FhirComponent extends AbstractApiComponent<FhirApiName, FhirConfiguration, FhirApiCollection> {

    @Metadata(label = "advanced")
    FhirConfiguration configuration;

This property appears to shadow a property of the same name on AbstractApiComponent

public abstract class AbstractApiComponent<E extends Enum<E> & ApiName, T, S extends ApiCollection<E, T>>
        extends DefaultComponent {

    @Metadata(label = "advanced", description = "Component configuration")
    protected T configuration;

This is an issue for me as I am attempting to register a IClientInterceptor to help with a SMART on FHIR workflow, which no longer works as the configuration supplied during class construction is ignored and a IGenericClient is never persisted.

To work around the issue in the interim, creating a component that extends FhirComponent, overriding the getClient method to utilise the configuration from AbstractApiComponent appears to resolve the issue.

Assuming I'm not missing anything obvious regarding the purpose for the configuration property on the FhirComponent class, and if desired, am more than happy to submit a PR with a fix.

Issue Links

• links to: GitHub Pull Request #6542