FhirEndpointConfiguration fails with AmbiguousBeanException for SSLContextParameters despite secure=false

[Ralf Steppacher]

Hello all,

I have a problem with org.openehealth.ipf.platform.camel.ihe.fhir.core.FhirEndpointConfiguration.java: On line 167 (current master) the code attempts to find an SSLContextParameters bean by type if no sslContextParameters query parameter has been specified, irrespective of the value of the secure flag. In our case we set secure=false, but we have multiple instances of type SSLContextParameters in our Spring context for other purposes. Which leads to an AmbiguousBeanException for a bean we don't need/want.

Probably the secure flag should be included in the conditional statement that guards the lookup of the bean by type, skipping the block if secure=false?

Thanks!

Ralf

[Christian Ohr]

Absolutely.

Will fix that on 3.6 and master.

thanks

Christian

--
You received this message because you are subscribed to the Google Groups "ipf-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ipf-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ipf-dev/1721160a-a6e2-409c-94bc-ebf13aca734f%40googlegroups.com.

[Ralf Steppacher]

Thanks!

Ralf

On Tuesday, August 6, 2019 at 5:26:49 PM UTC+2, Christian Ohr wrote:

Absolutely.

Will fix that on 3.6 and master.

thanks

Christian

Am Di., 6. Aug. 2019 um 16:44 Uhr schrieb Ralf Steppacher <ralf.st...@swisscom.com>:

Hello all,

I have a problem with org.openehealth.ipf.platform.camel.ihe.fhir.core.FhirEndpointConfiguration.java: On line 167 (current master) the code attempts to find an SSLContextParameters bean by type if no sslContextParameters query parameter has been specified, irrespective of the value of the secure flag. In our case we set secure=false, but we have multiple instances of type SSLContextParameters in our Spring context for other purposes. Which leads to an AmbiguousBeanException for a bean we don't need/want.

Probably the secure flag should be included in the conditional statement that guards the lookup of the bean by type, skipping the block if secure=false?

Thanks!

Ralf

--
You received this message because you are subscribed to the Google Groups "ipf-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ipf...@googlegroups.com.