You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by rlstephens <rl...@gmail.com> on 2016/10/19 17:08:19 UTC
camel-ahc Component Documentation
Hello!
I am upgrading our Camel services to use 2.18.0. We have a service that uses
the camel-ahc component to send SMS alerts via a webservice call.
Route building was failing after upgrade due to a change in the way the
endpoint handles realm properties. Current documentation specifies using
clientConfig.realm.x for realm options. This gave me Route errors about bad
realm parameters.
I noticed AhcClientConfigRealmUriTest was changed with the AHC 2.x upgrade
commit to use realm.x instead of clientConfig.realm.x. This worked fine for
me.
Could somebody please update the documentation with the new realm.x
parameters?
Thanks!
Ryan
--
View this message in context: http://camel.465427.n5.nabble.com/camel-ahc-Component-Documentation-tp5788978.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: camel-ahc Component Documentation
Posted by Claus Ibsen <cl...@gmail.com>.
You are welcome to do a PR to update the docs at
https://github.com/apache/camel/blob/master/components/camel-ahc/src/main/docs/ahc-component.adoc
We love contributions
http://camel.apache.org/contributing
On Wed, Oct 19, 2016 at 7:08 PM, rlstephens <rl...@gmail.com> wrote:
> Hello!
>
> I am upgrading our Camel services to use 2.18.0. We have a service that uses
> the camel-ahc component to send SMS alerts via a webservice call.
>
> Route building was failing after upgrade due to a change in the way the
> endpoint handles realm properties. Current documentation specifies using
> clientConfig.realm.x for realm options. This gave me Route errors about bad
> realm parameters.
>
> I noticed AhcClientConfigRealmUriTest was changed with the AHC 2.x upgrade
> commit to use realm.x instead of clientConfig.realm.x. This worked fine for
> me.
>
> Could somebody please update the documentation with the new realm.x
> parameters?
>
> Thanks!
> Ryan
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-ahc-Component-Documentation-tp5788978.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: camel-ahc Component Documentation
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
Hello,
The documentation now is generated automatically through the source code.
You can take a look here:
https://github.com/apache/camel/blob/camel-2.18.x/components/camel-ahc/src/main/docs/ahc-component.adoc
We will leave confluence soon and we will use new documentation on a new site.
Anyway the documentation need to be updated, because I still see references to com.ning package, while AHC 2.x has a new groupId and packaging.
Thanks for spotting this.
Cheers,
--
Andrea Cosentino
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, October 20, 2016 10:12 AM, rlstephens <rl...@gmail.com> wrote:
Hello!
I am upgrading our Camel services to use 2.18.0. We have a service that uses
the camel-ahc component to send SMS alerts via a webservice call.
Route building was failing after upgrade due to a change in the way the
endpoint handles realm properties. Current documentation specifies using
clientConfig.realm.x for realm options. This gave me Route errors about bad
realm parameters.
I noticed AhcClientConfigRealmUriTest was changed with the AHC 2.x upgrade
commit to use realm.x instead of clientConfig.realm.x. This worked fine for
me.
Could somebody please update the documentation with the new realm.x
parameters?
Thanks!
Ryan
--
View this message in context: http://camel.465427.n5.nabble.com/camel-ahc-Component-Documentation-tp5788978.html
Sent from the Camel Development mailing list archive at Nabble.com.