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

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

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.

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

[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)

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.

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. ___

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

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,

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

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