Web-service Architecture and Functionality

Asked

Viewed 40 times

0

I have a question about Web-service.

This is the following I have an application in Java EE JSP, where you should allow a conversation with another application on Android (Example: when registering a meeting minutes in the database by the JSP application, notify in the Android APP and have a user option view, the status of the meeting report).

I do not know if it is correct: I created a web-service within the JSP project, which is ready (this project makes several transactions such as registering, consulting, changing and deleting data, etc).

The question is should I have three apps for communication between it?

1º create an independent web-service to integrate the JSP project with the Android project;

2nd Independent JSP Project and Independent Android Project.

java jsf web-service web-application jsp

  • Why the tag [tag:jsf] ?

  • 1

    In this same JSP project, which I mentioned, I am using JSF with Primefaces for an event calendar. I tagged because someone who works with JSF could also help clarify the doubt. Thank you!

1 answer

0

Joshua,

Yes, your thinking is not incorrect, in fact, it is even a common architecture. I will advise you on the focus of each project so that the responsibility of each project is well defined and so that you can better absorb the opportunities.

Think about centralizing all the business model and rules on the web service model layer. In several situations this will enable simpler maintenance when any rule changes, as you only need to upgrade 1 project.

The Android app and JSP project will become simple, focusing more on the visuals. Which is especially good for the Android app, because depending on the type of processing you need to do, a server is obviously more robust than a smartphone or tablet (but I believe that’s not the case with your project, just an additional thought).

You could even do the web service and the JSP project in a single project, because following MVC, what would be your JSP project would be more focused on the View and the Controller could be implemented in Restful format, for example, and so would allow an Android app to request it. It’s a case to consider the possibility.

From what I could understand of your problem, I believe that this is information that would make you reflect a little more. Anything leave a comment!

  • Younger, thank you so much for helping me! I will follow the web-service idea and the JSP project in a single project, because it will be better. The JSP project, which I have is quite ready to trade following MVC. Each object, already runs its complete methods (CRUD). Any news regarding this topic I’ll pass you here! OK?

  • Younger, for this context the implementation in Restful format is better, than SOAP?

Browser other questions tagged java jsf web-service web-application jsp

You are not signed in. Login or sign up in order to post.