Hi, I think you can take a look at the camel-twitter component codes. As you know there are lots APIs which are provided by twitter. It calls the different API by looking up the path of the uri.
For the operation part , I think it is OK, and you should support override the operation through the message header. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Monday, February 25, 2013 at 3:58 AM, Joe San wrote: > Camel Riders, > > I need you suggestions on the URI options that I should consider for this > component. Taking a look at the following url: > > https://www.x.com/developers/paypal/documentation-tools/paypal-sdk-index > > It can be seen that there are different API products. I would assume that > we would be providing integration for all those listed. To start with, I'm > working on the Adaptive Payments API. What would be the best way to use the > uri for this camel component? Currently I intend to do so: > > paypal://adaptivepayments?operation=pay > > Later when I develop the Invoice API integration, it would be another > sub-component inside the camel-paypal project and the Endpoint URI would > look like: > > paypal://invoice?operation=getInvoiceDetails > > Is this approach good enough? Please offer your suggestions. > > Regards, > Jothi
