Saving Java data without a corporate server?

What solutions exist to save data without the need for a full-scale corporate server? I am new to Java. On uni, the entire curriculum was based on Java, so I already encoded a bit. But he never delved into the accessible framework. The only way we really dealt with perseverance was to use the vanilla JDBC connections.

I did some operations and found typical solutions. Most notably, "JAXB", "JPA", "Hibernate" and "TopLink". As far as I can tell, the last two actually implement "JPA", which is just a specification. I'm here?

All the tutorials I have found so far explain this quite well, and I have to say that I really like JPA. But all the tutorials I saw explained it all with the help of web pages. However, I am looking for a swing solution. Without webstart or the like. I would like to create a standalone application for Java applications. Given the target audience and requirements, I do not need a client / server architecture.

Now there is a Beans Binding theme. Which, for me, looks fun. Even though you must manually trigger the "PropertyChanged" events manually. Honestly, I don't care about the few lines added.

So ... to create a standalone desktop, save (and read) data from existing legacy databases:

What are your guidelines for structures / libraries / specifications?

  • JPA?
  • Jdbc?
  • Beans Binding?

Another important thing: the primary database to which I will write the application contains the Mutliple Inheritance Table and Slowly Changing Dimensions. I already drew with TopLink, and the results are fine. But I want to get rid of the application server.

... oh and ... is it possible to use Beans snapping in conjunction with objects? Creating read / write properties?

+4
source share
2 answers

I recommend JPA - although it is a standard, it is completely separate from the entire Java EE specification. You do not need an enterprise application server to use it. In fact, Sun has Using JPA in desktop applications .

+5
source

JPA + Hibernate, Derby in Java Database, Swing destop App. After annotating my model classes and defining a derby driver and such little things in XML files, stability was fully automated.

0
source

Source: https://habr.com/ru/post/1300420/


All Articles