Re: [Architecture] Connector:NetSuite
Also, what's the selection criteria for the supported operations. - searchMoreWithId is not useful on it's own. search function must be supported for this to be useful. - Following methods are frequently used in NetSuite integration projects as most NS accounts carry customization or addons - getCustomizaton - getCustomizationId - getSelectValue - initialize/initializeList is required for integration using most transaction record types Also, the following operations aren't as frequently used (they are actually recent additions to the API and not widely adopted yet): - *getBudgetExchangeRate* - *getCurrencyRate * - *getConsolidatedExchangeRate* *getPostingTransactionSummary * is useful for generating reports, but should be lower priority as well due to the limited use cases it'll support On Wed, Jun 4, 2014 at 11:10 AM, Shevan Goonetilleke she...@wso2.com wrote: Can you please list out the methods that were not selected (don't have access to the API documentation). Thanks Shevan On Wed, May 28, 2014 at 6:38 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* SuiteTalk exposes NetSuite as a data source for programmatic access, hence most of the data operations developers expect, such as insert, update, delete, and select/search are supported. There are also a number of operations that are available as supporting operations for data read/write operations. *API (SOAP)* https://system.na1.netsuite.com/app/help/helpcenter.nl?topic=CARD_-29 *Netsuite Connector Summary* • Connector Name: netsuiteconnector-1.0.0 • Version: 1.0.0 • Technology: SOAP *Authentication* Use Request Level Credentials which are sent in SOAP header while maintaining https proxy. *Methods* *addList *- Use to add one or more records into the system. The system returns a NetSuite identifier (internalId) that is unique for each record created within a record type. *attach *- Use to attach another record or file to/from another record *detach *- Use to detach another record or file to/from another record *deleteList *- Use to delete one or more records in the system. The records to be deleted are identified by either the internal or external ID and the record type. *getList *- Use to query the system for one or more records. You must provide either the internal or external ID and the record type for each query item. *getAll *- Use to return a list of records that do not have a search interface. *getBudgetExchangeRate*- Use to get and filter all data related to the Budget Exchange Rates table. *getCurrencyRate *- Use to get currency exchange rates from the Currency Exchange Rate table. *getConsolidatedExchangeRate* - Use to get and filter all data related to the Consolidated Exchange Rates table. *getItemAvailability *- Use to retrieve the inventory availability for a given list of items. *getPostingTransactionSummary *- Use to retrieve a summary of the actual data in an account. *searchMoreWithId *- Used to retrieve more records after an initial search operation is invoked. *updateList *- Use to update one or more existing records in the system by providing new values for the fields to be updated for each record. The records to be updated are identified by either the internal or external ID and the record type. *getDataCenterUrls *- Use for dynamic discovery of data-center-specific URLs for partner applications' access to NetSuite. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-NetSuite-tp97380.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- *Sameera Perera* Director of Engineering gtalk: samee...@wso2.com Tel : 94 11 214 5345 Fax :94 11 2145300 *WSO2, Inc.* http://wso2.com/ lean.enterprise.middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonSQS
Hi Shevan, Yes, we can delete single message using the *deleteMessageBatch * method. (You can pass one entry _id in that case). Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSQS-tp97657p97822.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonSQS
Hi, IMO, even though queue URL can be retrieved from the *listQueues* method, it will be useful if we can have *getQueueUrl* operation also in the implementation since most of the operations use queue URL as an input parameter. Other than that, selected operation list looks good to proceed with. Thanks On Wed, Jun 4, 2014 at 10:57 AM, Shevan Goonetilleke she...@wso2.com wrote: can we delete a single message using the *deleteMessageBatch method? On Mon, Jun 2, 2014 at 6:56 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* Amazon Simple Queue Service (Amazon SQS) is a messaging queue service that handles message or workflows between other components in a system *API (REST)* http://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/Welcome.html *AmazonSQS Connector Summary* • Connector Name: amazonsqs-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* This uses the standard HTTP Authorization header to pass authentication information. Developers are issued an AWS access key ID and AWS secret access key when they register. For request authentication, the AWSAccessKeyId element identifies the access key ID that was used to compute the signature and, indirectly, the developer making the request. *Methods Selected* Following methods are selected for the first version of this connector. *Permission* addPermission - Adds a permission to a queue for a specific principal. This allows for sharing access to the queue. removePermission - Revokes any permissions in the queue policy. *Queue* createQueue - Creates a new queue, or returns the URL of an existing one. getQueueAttributes - Gets attributes for the specified queue. setQueueAttributes - Sets the value of one or more queue attributes. listQueues - Returns a list of your queues. deleteQueue - Deletes the queue specified by the queue URL, regardless of whether the queue is empty. *Message* SendMessageBatch - Delivers a message to the specified queue. receiveMessage - Retrieves one or more messages from the specified queue. deleteMessageBatch - Deletes multiple messages. *Methods not selected* Following methods have not been considered for first version. *getQueueUrl *- Returns the URL of an existing queue. Queues can also be retrieved using *listQueues *method and hence this is not considered. *listDeadLetterSourceQueues *- Returns a list of your queues that have the RedrivePolicy queue attribute configured with a dead letter queue. The results of this method can also be retrieved through *getQueueAttributes *method. Hence this is not considered. *sendMessage *- Delivers a message to the specified queue. This functionality can be achieved through sendMessageBatch method. Hence this method is not selected. *changeMessageVisibility* / *changeMessageVisibilityBatch *- Changes the visibility timeout of message(s) in a queue to a new value. Since these methods are at configuration level, we have not considered. *deleteMessage *- Deletes the specified message from the specified queue. The same functionality can be achieved *deleteMessageBatch *method. Hence we have not considered this for the first version. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSQS-tp97657.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Sewwandi Perera Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:NetSuite
Hi Sameera, Sameera Perera wrote - searchMoreWithId is not useful on it's own. search function must be supported for this to be useful. We will include the search method. We were under the impression that search is not supported when using stateless authentication, but we have been able to clarify that it is possible to run the search method. Sameera Perera wrote - Following methods are frequently used in NetSuite integration projects as most NS accounts carry customization or addons - getCustomizaton - getCustomizationId - getSelectValue - initialize/initializeList is required for integration using most transaction record types We will include these methods. Sameera Perera wrote Also, the following operations aren't as frequently used (they are actually recent additions to the API and not widely adopted yet): - *getBudgetExchangeRate* - *getCurrencyRate * - *getConsolidatedExchangeRate* We will remove these methods. Sameera Perera wrote *getPostingTransactionSummary * is useful for generating reports, but should be lower priority as well due to the limited use cases it'll support So shall we remove this from v1 of the connector? Our reasoning behind including this was that generating reports would be a useful functionality for a connector, specially when integrating with other APIs. Thank You. On Wed, Jun 4, 2014 at 11:10 AM, Shevan Goonetilleke lt;shevan@gt; wrote: Can you please list out the methods that were not selected (don't have access to the API documentation). Thanks Shevan On Wed, May 28, 2014 at 6:38 PM, Rasika Hettige lt;rasikah@gt; wrote: *Introduction* SuiteTalk exposes NetSuite as a data source for programmatic access, hence most of the data operations developers expect, such as insert, update, delete, and select/search are supported. There are also a number of operations that are available as supporting operations for data read/write operations. *API (SOAP)* https://system.na1.netsuite.com/app/help/helpcenter.nl?topic=CARD_-29 *Netsuite Connector Summary* • Connector Name: netsuiteconnector-1.0.0 • Version: 1.0.0 • Technology: SOAP *Authentication* Use Request Level Credentials which are sent in SOAP header while maintaining https proxy. *Methods* *addList *- Use to add one or more records into the system. The system returns a NetSuite identifier (internalId) that is unique for each record created within a record type. *attach *- Use to attach another record or file to/from another record *detach *- Use to detach another record or file to/from another record *deleteList *- Use to delete one or more records in the system. The records to be deleted are identified by either the internal or external ID and the record type. *getList *- Use to query the system for one or more records. You must provide either the internal or external ID and the record type for each query item. *getAll *- Use to return a list of records that do not have a search interface. *getBudgetExchangeRate*- Use to get and filter all data related to the Budget Exchange Rates table. *getCurrencyRate *- Use to get currency exchange rates from the Currency Exchange Rate table. *getConsolidatedExchangeRate* - Use to get and filter all data related to the Consolidated Exchange Rates table. *getItemAvailability *- Use to retrieve the inventory availability for a given list of items. *getPostingTransactionSummary *- Use to retrieve a summary of the actual data in an account. *searchMoreWithId *- Used to retrieve more records after an initial search operation is invoked. *updateList *- Use to update one or more existing records in the system by providing new values for the fields to be updated for each record. The records to be updated are identified by either the internal or external ID and the record type. *getDataCenterUrls *- Use for dynamic discovery of data-center-specific URLs for partner applications' access to NetSuite. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-NetSuite-tp97380.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@ https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@ https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- *Sameera Perera* Director of Engineering gtalk: sameerap@ Tel : 94 11 214 5345 Fax :94 11 2145300 *WSO2, Inc.* lt;http://wso2.com/gt; lean.enterprise.middleware ___ Architecture mailing list Architecture@
[Architecture] Connector:Magento
*Introduction* Magento is an open source e-commerce web application. It is a content management system (CMS) based on PHP and MySQL for web hosting service, which was built using parts of the Zend Framework.It provides full support for object-oriented programming and Model-View-Controller (MVC) architecture. *API (REST)* http://www.magentocommerce.com/api/rest/introduction.html *Magento Connector Summary* • Connector Name: magento-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* Magento REST API uses 3-legged OAuth 1.0a protocol to authenticate the application to access the Magento service. *Methods Selected:* *Products* *createProduct* - Create a new Product. *updateProduct* - Update an existing Product. *deleteProduct* - Delete an existing Product. *listProducts* - List products existing within the instance. *getProduct* - Get details for a single product. *Product Categories* *getProductCategory *- Get categories a specific product falls under. *addCategoryToProduct *- Add a category to a specific product. *deleteCategoryFromProduct *- Remove a product from a category. *Product Images* *getProductImages *- Retrieves details for images associated with a product. - Note: This method covers the functionality of *get*, *[store_image]get*, *[single_image]get* and *[store_image/single_image]get* *addProductImage* - Adds a single image to a product. - Note: This method also covers the functionality of *add* and * [store_image]add* *updateProductImage *- Updates details (and content) of a single image assigned to a product. - Note: This method also covers the functionality of * [single_image]update* and *store_image/single_image]update* deleteProductImage - Deletes a single image assigned to a product. Note: This method also covers the functionality of [single_image]delete and [store_image/single_image]delete *Orders* *listOrders *- Gets a list of orders. *getOrder *- Gets details of a single order by ID. *Order Addresses* *getOrderAddresses* - Retrieve information about billing and shipping addresses of the required order. - Note: This method also covers the functionality of *get* , *[shipping]get* and *[billing]get* *Order Comments* *getOrderComments* - Get comments assigned to an order. *Order Items* *getOrderItems* - Get items for an order. *Inventory* *listStockItems *- Retrieve a list of existing stock items. *getStockItem *- Get details of a single stock item by ID. *updateStockItem *- Update details for a single stock item. *Customer Addresses* *listCustomerAddresses *- Lists addresses defined for a customer. *addCustomerAddress *- Adds a new address for a customer. *updateCustomerAddress *- Updates a single customer address by address ID. *deleteCustomerAddress *- Deletes a single customer address. *Customers* *getCustomer* - Get details of a single customer *createCustomer * - Creates a new Customer *updateCustomer * - Updates details of a single customer *deleteCustomer * - Deletes a single customer. *Methods not selected:* *Product Websites* *get ,add [Website Assignment with Product Data Copying]add ,[Multi-Website Assignment]add ,[Multi-Website Assignment with Product Data Copying]post*, and *delete* methods disregarded from the first version as they are supporting one time entry functionalities. *[single]get *- Functionality of this method is covered under listOrders method. *[single]get* - Functionality of this method is covered under listCustomerAddresses method. *listCustomers* - This method is ignored from the first version as it has a less business value than the getCustomer method . Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Magento-tp97825.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonSQS
Thanks Sewwandi, will include *getQueueUrl* method if it has a business importance. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSQS-tp97657p97826.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:GooglePrediction
Thanks Shevan, will proceed with this method list. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-GooglePrediction-tp97528p97828.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonSQS
Hi all, AFAIR, message deletion is based on message visibility timeout value. You get a message from queue and then if you failed to delete that message before visibility timeout period, message is not deleted and it is available for other consumers to retrieve. So we have to expose message visibility timeout related methods too. thank you. On Wed, Jun 4, 2014 at 12:54 PM, Rasika Hettige rasi...@gmail.com wrote: Thanks Sewwandi, will include *getQueueUrl* method if it has a business importance. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSQS-tp97657p97826.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Magento
Magnto REST doesn't cover most important sections like sales in detail, why can't we try their SOAP?? it cover almost everything http://www.magentocommerce.com/api/soap/introduction.html *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Wed, Jun 4, 2014 at 12:40 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* Magento is an open source e-commerce web application. It is a content management system (CMS) based on PHP and MySQL for web hosting service, which was built using parts of the Zend Framework.It provides full support for object-oriented programming and Model-View-Controller (MVC) architecture. *API (REST)* http://www.magentocommerce.com/api/rest/introduction.html *Magento Connector Summary* • Connector Name: magento-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* Magento REST API uses 3-legged OAuth 1.0a protocol to authenticate the application to access the Magento service. *Methods Selected:* *Products* *createProduct* - Create a new Product. *updateProduct* - Update an existing Product. *deleteProduct* - Delete an existing Product. *listProducts* - List products existing within the instance. *getProduct* - Get details for a single product. *Product Categories* *getProductCategory *- Get categories a specific product falls under. *addCategoryToProduct *- Add a category to a specific product. *deleteCategoryFromProduct *- Remove a product from a category. *Product Images* *getProductImages *- Retrieves details for images associated with a product. - Note: This method covers the functionality of *get*, *[store_image]get*, *[single_image]get* and *[store_image/single_image]get* *addProductImage* - Adds a single image to a product. - Note: This method also covers the functionality of *add* and * [store_image]add* *updateProductImage *- Updates details (and content) of a single image assigned to a product. - Note: This method also covers the functionality of * [single_image]update* and *store_image/single_image]update* deleteProductImage - Deletes a single image assigned to a product. Note: This method also covers the functionality of [single_image]delete and [store_image/single_image]delete *Orders* *listOrders *- Gets a list of orders. *getOrder *- Gets details of a single order by ID. *Order Addresses* *getOrderAddresses* - Retrieve information about billing and shipping addresses of the required order. - Note: This method also covers the functionality of *get* , *[shipping]get* and *[billing]get* *Order Comments* *getOrderComments* - Get comments assigned to an order. *Order Items* *getOrderItems* - Get items for an order. *Inventory* *listStockItems *- Retrieve a list of existing stock items. *getStockItem *- Get details of a single stock item by ID. *updateStockItem *- Update details for a single stock item. *Customer Addresses* *listCustomerAddresses *- Lists addresses defined for a customer. *addCustomerAddress *- Adds a new address for a customer. *updateCustomerAddress *- Updates a single customer address by address ID. *deleteCustomerAddress *- Deletes a single customer address. *Customers* *getCustomer* - Get details of a single customer *createCustomer * - Creates a new Customer *updateCustomer * - Updates details of a single customer *deleteCustomer * - Deletes a single customer. *Methods not selected:* *Product Websites* *get ,add [Website Assignment with Product Data Copying]add ,[Multi-Website Assignment]add ,[Multi-Website Assignment with Product Data Copying]post*, and *delete* methods disregarded from the first version as they are supporting one time entry functionalities. *[single]get *- Functionality of this method is covered under listOrders method. *[single]get* - Functionality of this method is covered under listCustomerAddresses method. *listCustomers* - This method is ignored from the first version as it has a less business value than the getCustomer method . Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Magento-tp97825.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Magento
Yes I also agree. It seems only subset is available via rest. Even though we are implementing limited methods it will be easy to extend if we use soap. @Rasika Have you guys checked both options? On Wed, Jun 4, 2014 at 9:36 PM, Dakshika Jayathilaka daksh...@wso2.com wrote: Magnto REST doesn't cover most important sections like sales in detail, why can't we try their SOAP?? it cover almost everything http://www.magentocommerce.com/api/soap/introduction.html *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Wed, Jun 4, 2014 at 12:40 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* Magento is an open source e-commerce web application. It is a content management system (CMS) based on PHP and MySQL for web hosting service, which was built using parts of the Zend Framework.It provides full support for object-oriented programming and Model-View-Controller (MVC) architecture. *API (REST)* http://www.magentocommerce.com/api/rest/introduction.html *Magento Connector Summary* • Connector Name: magento-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* Magento REST API uses 3-legged OAuth 1.0a protocol to authenticate the application to access the Magento service. *Methods Selected:* *Products* *createProduct* - Create a new Product. *updateProduct* - Update an existing Product. *deleteProduct* - Delete an existing Product. *listProducts* - List products existing within the instance. *getProduct* - Get details for a single product. *Product Categories* *getProductCategory *- Get categories a specific product falls under. *addCategoryToProduct *- Add a category to a specific product. *deleteCategoryFromProduct *- Remove a product from a category. *Product Images* *getProductImages *- Retrieves details for images associated with a product. - Note: This method covers the functionality of *get*, *[store_image]get*, *[single_image]get* and *[store_image/single_image]get* *addProductImage* - Adds a single image to a product. - Note: This method also covers the functionality of *add* and * [store_image]add* *updateProductImage *- Updates details (and content) of a single image assigned to a product. - Note: This method also covers the functionality of * [single_image]update* and *store_image/single_image]update* deleteProductImage - Deletes a single image assigned to a product. Note: This method also covers the functionality of [single_image]delete and [store_image/single_image]delete *Orders* *listOrders *- Gets a list of orders. *getOrder *- Gets details of a single order by ID. *Order Addresses* *getOrderAddresses* - Retrieve information about billing and shipping addresses of the required order. - Note: This method also covers the functionality of *get* , *[shipping]get* and *[billing]get* *Order Comments* *getOrderComments* - Get comments assigned to an order. *Order Items* *getOrderItems* - Get items for an order. *Inventory* *listStockItems *- Retrieve a list of existing stock items. *getStockItem *- Get details of a single stock item by ID. *updateStockItem *- Update details for a single stock item. *Customer Addresses* *listCustomerAddresses *- Lists addresses defined for a customer. *addCustomerAddress *- Adds a new address for a customer. *updateCustomerAddress *- Updates a single customer address by address ID. *deleteCustomerAddress *- Deletes a single customer address. *Customers* *getCustomer* - Get details of a single customer *createCustomer * - Creates a new Customer *updateCustomer * - Updates details of a single customer *deleteCustomer * - Deletes a single customer. *Methods not selected:* *Product Websites* *get ,add [Website Assignment with Product Data Copying]add ,[Multi-Website Assignment]add ,[Multi-Website Assignment with Product Data Copying]post*, and *delete* methods disregarded from the first version as they are supporting one time entry functionalities. *[single]get *- Functionality of this method is covered under listOrders method. *[single]get* - Functionality of this method is covered under listCustomerAddresses method. *listCustomers* - This method is ignored from the first version as it has a less business value than the getCustomer method . Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Magento-tp97825.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___
Re: [Architecture] Connector:Magento
Hi Malaka, As per the initial discussions on connectors, it was suggested to give the first priority on REST when you have both REST/SOAP. So we have considered REST here. Anyways, since there are less functionalities in REST, will do a further analysis on SOAP and come back to you. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Magento-tp97825p97860.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
