Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Pretty large question, and there's no real one answer. You really need to determine what are the needs of the app being built.</p> <p>As far as RMI, you need a server process which provides an RMI host. Glassfish provides one for you. But, if yo're using glassfish, you'd probably want to use JPA / EJB3 as the persistence layer. Which is simply Oracle's TopLink rebadged for the OpenSource world.</p> <p>I'm not sure Tomcat comes with an RMI layer, although it's been a bit since I've developed for Tomcat in anger. It's first and foremost a servlet engine. If you were looking at a REST interface between client and server, that would be a good choice (although Glassfish provides a servlet engine as well).</p> <p>If you really want to use Hibernate and you want RMI as the transport between client and server, don't discount Spring. It will have RMI server engines where you define your Spring beans which call into Hibernate. No Application Server required (apart from what Spring provides.</p> <p>As far as MVC is concerned, from the client perspective you have Swing handling the View, with native Java implementing the Model and Controllers. The Model, in this case, would be DTOs provided by the Services exposed by the RMI Server component. I would think that Hibernate would be limited to the Server process, and there would be little View in the Services. The Model in the Client code would be the DTO's and the surrounding framework which makes the RPCs to the services.</p> <p>Hope this helps</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COThank you very much for your idea, actually I'm developing an application which is much like an inventory management application in which the inventory will be accessed by many users with swing UI. And I've knowledge of hibernate and RMI but not of Spring and I've very limited time to complete the project. Is it worth learning Spring to develop this application than developing without Spring?
      singulars
    2. COBy all means, go with what you know, especially if there are time constraints. You wouldn't need to learn all of Spring. I would focus on their RmiServiceExporter (http://static.springsource.org/spring/docs/2.0.x/reference/remoting.html) which is just a simple way of binding your Java objects to an RMI service which is accessible publicly. You can use as much or as little of the Spring Bean functionality as you like. That said, it's pretty easy to pick up and once you start using it you probably won't look back.
      singulars
    3. COMore specifically, GlassFish Open Source Edition bundles EclipseLink, and Oracle GlassFish Server bundles TopLink. I 100% agree with not using Hibernate *UNLESS* there is a specific reason to do so. All quality tests that use JPA use EclipseLink to do so. One route to take is to use a REST API, and pass JSON data with the help of Apache Jackson. JSON parsing is going to be in Java EE 7, and JSON binding will be coming later so you won't even need Jackson down the road. Using REST is much more firewall friendly than RMI.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload