Willem.Jiang wrote > 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.
The first option would be a lot easier for me. If I define the Object with all those fields that I might have in the PayPal object, it looks like adding duplication. I'm wondering how a typical route to paypal would look like? In a typical web application, the user has to enter the values in the fields in the GUI. Once he clicks submit, I assume that the data is sent to the middle tier that performs some validations and the request object created. How could this now be applied to an integration scenario? Regards, Joe -- View this message in context: http://camel.465427.n5.nabble.com/Camel-PayPal-Component-tp5728062p5735472.html Sent from the Camel Development mailing list archive at Nabble.com.
