I have a small application with a scaffold frontend and a RESTful Controller. I have switched to a Vaadin frontend and now the REST service is unreachable since the url mappings have been removed. Any chance to get it back without running a second application with the domain classes as plugin?
Related
I am running the frontend and backend modules for OSRM. I want to make some customizations for the web interface and connect it to the backend functions. In which part of the project should I make these changes?
I want the gwt app to call a spring boot rest service with basic authentication which consumes and produces a json object and is deployed on a seperate server from the gwt app.
Any hints on how this can be done ?
There is a library called restygwt to easily define REST calls. I think there is an easy way to set the 'Basic' header.
I developed a dynamic web project in eclipse java EE ide as index.jsp, when I run it on Tomcat Server7.0 server it says http://localhost:8080/filename/ something. is that what they mean by REST? or do I need Spring to run a REST ?. rest is what that comes in a url, if i provide this url in my browser it opens the file, then why I can't call it as rest service?
Restful is an architectural style that make in disposition through HTTP a number of resources under different formats, usually json, to set or retrive the ressources, simple http operations (PUT, GET, POST, and DELETE. PUT) could be used for that.
I recommend you to use JAX-RS, but here u can see how to work with rest web service with Spring:
Building a RESTful Web Service Spring
Our architecture consists of several backend (non-ServiceStack) services and applications that send data to our system via ServiceStack service hosted in asp.net - this is currently a standalone ServiceProject project containing our required Services/Repository/DTOs following the structure of all the provided ServiceStack samples.
With our backend complete we're now designing our two front-end requirements consisting of a web application and native mobile application. For the web application I'd really like to continue leveraging ServiceStack by using the Razor plugin to create the application's layout/views from our existing DTOs, for our mobile app we will only rely on the ServiceStack service for authentication and data - as it is native it's layout/views will come from it's own SDK.
Can I leave my standalone ServiceStack service as is and:
Create a separate web application project that authenticates
against our existing standalone ServiceStack service and uses the
Razor view plugin?
Have our native mobile app clients
authenticate against the same standalone ServiceStack service?
Most of the examples ie. RazorRockstars I've seen have the services embedded in the web project so I'm not sure if this distributed type of setup is supported. Any guidance or feedback on this is greatly appreciated!
It is very much possible. You can consume the web service from both, web and native mobile application. I worked in a ASP.NET MVC web application which used to make call to Web API service hosted at different server. The Web API service was shared among multiple applications. We were consuming it by making AJAX calls from client.
Something similar to your scenario is done at below link but they are using cloud to host service:
http://www.codeproject.com/Articles/529109/Mobile-2fWebplusClient-2cplusWebplusAPIplusandplus
If you have opportunity to make a web app for mobile instead of native app, then in a single solution both mobile and desktop app can be created. The exemplary solution can be found here: http://nopcommerce.codeplex.com/
Thanks and free free to discuss more in case of further questions.
I am creating a web application in eclipse (via dynamic web project wizard). the Main job of this web app is to call an External web Service's Methods. to accomplish this task should i make an EJB which will call this web service or should i go with creating a Web Service Client. what are the best practices and recommendations.
Keep it simple - just create a web service client. Unless you have reasons for using EJBs (perhaps distributed transactions) you are over-engineering. You can always add this later if you need it.
you can simply use Java Jersey for this. Here goes a clean tutorial