Call external web service with Sencha Cmd application

Question

I created an ExtJS 5 application with Sencha Cmd. I will deploy this application in a tomcat server where there are some REST web services. I would need to use these web services but when I run the application with "sencha app watch" (on port 1841) it doesn't find the services because they are on a differente server (tomcat is on a different port). How can I use an "external" web service with Sencha CMD? Thanks stefano

Answer 1

Here are some of the available options:

Option 1 Proxy Web Service

You could create a service on the local machine where the sencha app is that create web requests that then goto the target remote services. This is called a proxy service.

Essentially the proxy service will take a request and resubmit it to the desired target remote machine.

There is a php example here

And a C# web request example here (Although this c# example isn't exactly what you are needing. The base of the web request that would need to be submitted is in this code. )

Option 2 JsonP

The other option off the top, is if the web services on the other machine support jsonp they should be accessible. However, jsonp only supports get so if you have a full rest implementation some services will probably not work.

More information on jsonp

And an extjs request example for JsonP:

Ext.data.JsonP.request({
            'url': 'url',
            params: {
                'param1': 'value'
            },
            success: function (result, request) {
                //success
            }
        });

Option 3 Hosting multiple apps/paths on single port

However, since it seems like the tomcat server may actually be on the same machine. Is there not a way to host both the web services and the application path through tomcat?

It looks like, for instance, jetty has an option to host two apps on the same port

Option 4 Enable CORS

You can enable cross origin resource sharing on the rest application depending on the architecture/framework used.

The browser will basically send a request first to see if it can access the resource. And then the server would respond with the allowed origin domains. Once CORS is enabled then access could be granted between the two different ports/servers

Great site on CORS with instructions for enabling on most basic setups

Here is example documentation for spring