Technology used for developing server in java in tresvant?
Learn Java and decided in the process to implement an application in three-tier architecture client-server-database. The application is purely academic — for example, the client application of the librarian (a list of books, location of books, visitors). Thick client + database already implemented, so you want to bother with trehdverka. The idea of the whole logic, filtering, and manipulation of data should be dealt with the server? The client is responsible only for displaying data. Base for storing them.
Client — rich swing
What technologies should I learn/try to develop the server part? If I understand correctly — I need to use an application server(glassfish/weblogic/jboss)? Also in the future I would like to expand the functionality of the web thin client(but with few other functions, not duplicating the desktop, point to administrative tools, for example)
Technology that you need to study (at a minimum):
* JNDI-directory (it is prescribed jdbc-resource — address to the database)
* EJB (business layer, it just use hibernate, transactions)
* Servlets and JSP (display level data, in other words — generation of html-pages)
If the EJB all clear (to choose especially not anything else), for JSPS you can use the MVC libraries, among which are comfortable enough and with a large amount of documentation Struts2, Sprinc VMC, etc.
reba.Ruecker15 answered on October 8th 19 at 02:36
Let me say that the client-server architecture of such a plan yesterday, and the future of their unfortunate.
I'd studied pure webовские technology (as above already advised — EJB etc) and not bother with swing clients.
billy_Nicolas36 answered on October 8th 19 at 02:38
It is best to start with Spring, you do not suffer with this EJB and other obscurantism from J2EE. I spent 5 years working with J2EE and now switched to the Spring framework, so everything is simple, lightweight and most importantly it works.
Of J2EE we need to deal very well with Servlets, for understanding take Tomcat.
Also a good idea to understand what is IoC, loose-coupling.
JBoss or Glassfish are very hard decisions and at first it will be difficult to understand how it works. So better c understand Tomcat with Servlets, IoC, loose-coupling, for example Spring. And after that you already will be unnecessary JBoss or Glassfish.
harmony_Bayer4 answered on October 8th 19 at 02:40
The application server will be required.
vesta.Mann28 answered on October 8th 19 at 02:42
Suggest components to communicate through spring. Using spring easily export Your services via HTTP — web services or remoting hessian
Murphy28 answered on October 8th 19 at 02:44
A little not clearly, why then do we need a staging server, why not just query the database from the client. Filtering/sorting etc. is quite a are implemented through SQL queries
Or are there any additional requirements, like logging / integration with third party systems / complex business logic?
The simplest, of course, EJB
If you want more freedom — then Spring