.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368p5770254.html
Sent from the Camel - Users mailing list archive at Nabble.com.
king for is a way of utilising the mechanism Camel uses
> internally, when not using CxfEndPointConfigurer to establish the SSL
> configuration.
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368p
uses
internally, when not using CxfEndPointConfigurer to establish the SSL
configuration.
--
View this message in context:
http://camel.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368p5770215.html
Sent from the Camel - Users mailing list archive at Nabble.com.
the conduit isn't used. This seems like a
> bug to me.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368p5756914.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
h the specific
names of the conduits then it does work how I would expect. For whatever
reason, if the name is a wildcard the conduit isn't used. This seems like a
bug to me.
--
View this message in context:
http://camel.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368p5756914.html
point is created programmatically. Is
> that true or do I have something configured incorrectly?
>
> I realize this is pretty complicated, if there's anything I can do to help
> clarify this, please let me know. Thank you so much!
>
>
>
> --
> View thi
omplicated, if there's anything I can do to help
clarify this, please let me know. Thank you so much!
--
View this message in context:
http://camel.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368.html
Sent from the Camel - Users mailing list archive at Nabble.com.