Stephan van Hulst wrote:Sure, a REST API is one way to do it. You can use JAX-RS to communicate between the client and the web service. For the service, use the annotations defined in javax.ws.rs. You can create a client using ClientBuilder.
If you run the service in Tomcat, you can use Jersey as the JAX-RS implementation.
I've also found something called EclipseLink JPA-RS, which seems to be a technology for quickly setting up a web service for the sole purpose of interacting with a database. It might be just what you're looking for, but personally I'm wary of it because I don't like my web API to be so tightly coupled with the database.
Robert Ilin wrote:So basically the web service acts as a 'server'?
The server and the client app should be 2 different projects in Eclipse or in the same project?
And another thing the content of the learning app will be generated dynamically based on some config files. Where to store these config files? I don t think it s a good idea to store them on the client side app because I don t want the client to access these files.
Robert Ilin wrote:And if the projects are separated, how will I access the classes from the library project let s say in the Client app?
Robert Ilin wrote:I thought this is a good approach since if I want to modify some content I don t need to modify the code but only the files.
and use it to draw the java fx interface whenever a resource is needed
Is it a good approach to load all the content of the config files on startup or do you suggest a better approach?
Stephan van Hulst wrote:I can give you a quick start. You just need to tell me which application server you want to use. Tomcat is usually enough for most web applications.
I found some pretty shells, some sea glass and this lovely tiny ad:
Two software engineers solve most of the world's problems in one K&R sized bookhttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton