It could be easy if the application can use the PayPal API type class directly, then you don't need to convert the request object any more. If it doesn't , I think you can just define the Object with the basic information of payment, such as the user information (email, phone), the payment amount, currency, etc.
-- 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 Wednesday, July 10, 2013 at 6:53 PM, Jothi wrote: > Willem.Jiang wrote > > Basically, you just need to find a way to convert the application payment > > information into the Request object that the SDK has, you can do the > > invocation without any issue. > > Now I suggest you can define a common request object for the other > > component to use, then your convertor can work for most cases. > > > > That exactly is where I'm stuck. What Object type should I expect from the > application that contains this application payment information? When I know > the Object type, I can write my converter to convert from that Object type > to the PayPal Request object that I can use for invoking the service. > > Thanks for taking a look into this! > > Regards, > Joe > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-PayPal-Component-tp5728062p5735429.html > Sent from the Camel Development mailing list archive at Nabble.com > (http://Nabble.com).
