I would like to build a multilingual Quarkus Restful API, or GraphQL API, but i am wondering if there is a way to handle internationalization (i18n) in Quarkus for translating messages, responses?
Related
I´m using Microprofile-GraphQL extension (https://quarkus.io/guides/microprofile-graphql) for Quarkus together with Smallrye JWT (https://quarkus.io/guides/security-jwt) to secure my GraphQL endpoint.
This however blocks the Graphql UI that comes with the Microprofile extension under /graphql-ui
Is there any way to permitt / allow routes that are not defined in your own rest controllers?
Something like
quarkus.http.auth.permission.permit.paths=/graphql-ui/*
quarkus.http.auth.permission.permit.policy=permit
should do it, please see Quarkus Authorization
I want to learn the Spring Framework and therefore I decided to make a web application using it, but I don't want to use Spring MVC as it still uses JSP. What all projects from Spring can be used if I want to have a UI which can be made using React / Angular and the backend is managed by Spring.
You have to use REST API, and pass data to front-end JS framework via JSON.
Look here: https://spring.io/guides/gs/rest-service/
Start with creating a simple Rest Controller with Spring Boot.
Then you have to choose your JavaScript framework (jQuery, Angular, React),
and make a HTTP request to URL typed in your #RestController.
You can achieve this by using AJAX method from your JS framework.
Try this,it will speed up your development
Restful Web Service with Spring Boot
by the way,if you want to use Angular/React+Spring Boot you can use JHipster, this tool will just do the basic setup for your Angular/React+Spring Boot application in couple of minutes,the website has a clear video tutorial you can use it will only take about 15 min approx
Jhipster
Info about technologies available here:
Spring REST Docs link
Rest Assured link
Ktor backend link
Main question is:
Can I generate documentation with json payloads for ktor backend like I did it for Spring backend using Spring Rest Docs
Spring Rest Docs uses unit tests technique to generate json payload and descriptions snippets. This snippets in asciidoctor style used later for including to handwritten documentation.
Is there a way that make Spring generate documents of all my rest APIs automatically and set it as the error page?
Spring REST Docs is the tool to help you to produce documentation for your RESTful services that is accurate and readable.
An alternative is swagger, with the swagger annotion, it is eaiser to integrate with existing RESTful services and generated the swagger UI page.
Then customize the spring boot error page
This is my first question on StackOverflow and I hope someone can help me. :-)
I am planning to build a web-application (backend) with spring roo. For the backend I will use Spring and Hibernate/JPA. In the future I will implement a web client (JSF/Primefaces), a mobile client (Android) and a Windows App.
With spring roo it is easy to create a layered architecture with domain classes, repositories and services. This part is fun.
But now I am thinking about remoting and how to connect all the clients (web, mobile, windows) with my backend.
1.) What do you prefer for the remoting between client and backend? SOAP-Web Services or a REST-API (e.g. with JSON).
2.) If REST-API: How should the API look like for authentication/login functionality? REST is resource-oriented but how do you implement authentication with REST API?
At the moment I think a REST-API is a good idea. Because I am using spring it is easy to create a Spring MVC controller with REST support. But is this the correct way to implement a REST API for all the three devices? The web client e.g. should be implemented with JSF and Primefaces and I don´t use spring MVC for the web layer.
3.)Can I nevertheless use Spring MVC controllers to build the REST API (together with JSF in the web layer)? Or is there a better way?
1.) What do you prefer for the remoting between client and backend? SOAP-Web Services or a REST-API (e.g. with JSON).
I don't have too much experience with SOAP-WS, but I have a ton of experience with REST-APIs using JSON. There are many implementations for mobile, web and server side clients that are fairly simple to implement.
2.) If REST-API: How should the API look like for authentication/login functionality? REST is resource oriented but how to implement authentication with REST API?
If you are already using spring, I recommend securing your API with Spring Security. You can use spring security even if you don't end up going with Spring MVC for your API implementation. There are many ways to secure a rest API with spring security, but I the simplest is to send the basic auth header with every request to a secure URI
3.)Can I nevertheless use Spring MVC controllers to build the REST API (together with JSF in the web layer)? Or is there a better way?
Spring MVC Controllers will work fine, but I would recommend going with RestEasy or Jersey. I find them to be more flexable.
I agree with #mad_fox. Additionally, i want to add another option regarding your question#2. If you dont want to use Spring security, you can write your own token based authentication mechanism using spring and basic java interceptors.
You can store the token in your browser local storage.