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

Database: Postgres.

ORM: Hibernate

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)
October 8th 19 at 02:32
6 answers
October 8th 19 at 02:34
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.
From personal experience I can recommend Glassfish, it seemed to me the most simple and straightforward. To use JBoss refused because there were problems with the plugins for Eclipse on my x64 machine (the plugin did not work correctly). - roslyn commented on October 8th 19 at 02:37
Thank you very much. This is great. Gone Google. Thanks again! - elnora_Hauck15 commented on October 8th 19 at 02:40
Why EJB? The entire business layer is easily done on JPA (hibernate) + Spring. - nikita.Stracke commented on October 8th 19 at 02:43
EJB to make it work in cluster and cloud technologies (load balancing between servers) through remote EJB and maintained a distributed transaction among all these things. - roslyn commented on October 8th 19 at 02:46
If I went to a booze, then from JNDI, EJB, JAAS, Servlets, JMS. Well, about the RMI does not hurt to read. - billy_Nicolas36 commented on October 8th 19 at 02:49
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.
I agree that the desktop is rooted in the past, but while IMHO, for the same "the library" simply buttons field. And IE8 will not allow for such responsiveness as a desktop. Therefore, I wish to deal with this, and then go on the web. - roslyn commented on October 8th 19 at 02:39
And what buttons and fields in the browser are different from buttons-field swing? (I'm not even going to raise the issue of servicesnote swing)
I work JavaWeb develop a very large application (>10 million rows) for business and believe that the browser UI already overtook desktop. We have there not only the buttons\the field, and a control keyboard at hotkey, pop-up dialogs, tabs, etc. etc. As for the response — is similar. For simple applications, the difference is imperceptible in General. For serious of course the difference in response, but the pros still more at times. - elnora_Hauck15 commented on October 8th 19 at 02:42
And what is your configuration of machine and browser. We have IE8 + Pentium Core2Duo is a small web application in Java. Users really swear, but can not change anything. The response speed is really low in the area of seconds when switching from one field to another. There's really more and usability to 0.
So that the situations and configuration are different. - nikita.Stracke commented on October 8th 19 at 02:45
We used to have support only IE, now all supported. By the way, for SAP products a response in a couple of seconds is the norm, but for every query and spend tens (sometimes hundreds) of thousands of lines of server code.

For small apps shouldn't be a problem. Can you explain the phrase "when you switch from one field to another"? Way because html and then Java? - roslyn commented on October 8th 19 at 02:48
Nobody says that it is the fault of Java. It is the fault of the browser. - billy_Nicolas36 commented on October 8th 19 at 02:51
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.
October 8th 19 at 02:40
The application server will be required.
Oops. Enter stuck.
The application server will need :)
Recommend, strongly recommend to use jboss/tomcat =) - roslyn commented on October 8th 19 at 02:43
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
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

Find more questions by tags Java