I am trying to implement a webservice in a Struts1 web application, but Struts intercept all actions.
¿Is any way to exclude specific paths as excludePattern in Struts2?
Related
I'm a Sitecore beginner, working on Sitecore 8 with ASP.NET.
There is a page where an Ajax call has to be made to get data.
Created a test web service in the project which responds to the ajax call with success. This service will be a wrapper.
I understand, I have to consume one of the 3 options (in the title) inside the test service, to get the Sitecore items and do stuff.
But all 3 appear similar to me & not sure which one to go with, to achieve my task
Also,
1. Is there an advantage of one over the other.
2. ..and when to use which one.
Sitecore Services Client is the framework or namespace that both Item Service and Entity Service sit within. Item Web API is the legacy framework.
Use Item service if you want to do basic stuff with the sitecore Items as this is a prebuilt api. Entity Service allows you to create your own API using the Sitecore.Services.Client framework and give you much more power and control.
https://mikerobbins.co.uk/2015/01/06/entityservice-sitecore-service-client/
Use can also use Sitecore.Services.Client to do the routing and you write the controller. see https://mikerobbins.co.uk/2015/06/25/sitecore-service-client-servicesapicontroller/
my GUI app communicate with taht webservice. for example
at GUI,
enter number : '1'
then the webservice send back
price : $10
quantity : 30
currently, the vendor webservice is not yet finished. but i need to test my GUI wheter the design looks good for the 'price' and 'quantity' column.
sorry that i am newbie in soapui and have no idea how to start, although i finished reading the tutorial.
Do I need to create a mockup webservice to start?
i got a webservice link from vendor (.asmx)
i open the .asmx link at IE and got the send and request xml format.
Can i make use of that xml in soapui? and how?
check out http://www.soapui.org/Getting-Started/mock-services.html to learn how to create a mock service from a wsdl.
If you do not have access to the vendor wsdl then you can use any other wsdl and create a mock service using that wsdl and just replace the xml with something your GUI expects.
Also, as your gui makes a call to the webservice, you would need to update the web service endpoint in your Application to point to the mock service.
Now just start up your mock service and away you go..
I have a bunch of RESTful JSON webservices created with Spring WebMVC and I wonder if there's any library or framework that could automatically generate web pages with forms to call these services and test them.
I know some application servers have web control panels that dynamically generate this kind of form when you deploy webservices to them, but I'm trying to find an open source solution that could be embedded in my web app and deployed a simple Tomcat or Jetty server.
I have a working JSP page (with one parameter). Now somebody wants to use my JSP as a webservice.
How can I create a WSDL for my JSP, and how do I passthrough parameters
I'm able to to create a WSDL and test it, but I'm unable to read my parameter request.getParameter in the JSP.
I would suggest looking into some existing framework, like axis2 or jax-ws, for creating web services. Doing SOAP manually tend to get...messy.
A friend wants to consume my ASP.NET MVC 2 application in a similar fashion as adding a web reference to it, accessing my functions, and using my model objects from a .Net web form from a separate website.
Any links out there that could explain how to "dress" my MVC responses so that his server to server consumption would be similar in experience to a web service?
I suggested using System.Net.WebClient to pull the results in to a variable then deserialize the JSON result, but maybe there's a better approach out there?
I'd suggest that you consider an API controller or a separate API application depending on the load you expect from people consuming data from your application. A separate API application will allow you to move it off your application servers if needed.
Rarely, will you find that the data that you would provide via an API is a one-to-one match with what your views need to be rendered. Behind the scenes you could abstract the data generation so that your API and your application controllers reuse the same code to get at the data, but the front-end of the API would understand how to negotiate security (from an API perspective) and present data that is easily consumed by a program. Moreover, you won't find that you're creating extra controllers and methods in your application just to provide some data that will never be used in a particular view.
You could use MVC or WCF for the API and JSON or XML as the payload format. If you use WCF, you get the benefit that he really can simply add a service reference to connect to it without you having to build a WSDL file/action.
From another's advice, Phil Haack added this to MVC 2 Futures. Add the DLL reference to the Application Start, and bingo. It uses a validator.