Hey there,
i asked google quite a lot, but wasn't able to get some really good ressources on what is the best practice and what is really a feasible solution... So here my Scenario, as simple as it sounds :D
What is the best approach, having a Client/Server Architecture with Hibernate as persistence Layer and a Client e.g. using Swing.
I found a lot on lazy-loading/RMI/etc. but most of the articles already 5 years old. I guess/hope, using more recent Hibernate versions will provide some awesome techniques.. ;)
Are there Arcticles you can recommend or what would your approach look like?

best regards and thank you

Why should there be changes? If only "server-side" knows your database and you have lazy-loading in use you have to do these same things you did five years ago. The problem of transaction lifetime and extended contexts is the same as before.

Thanks for your anwser.
What i was thinking about, whether there might be some kind of a library or so that helps in transferring objects fetched with hibernate on server-side to the client. As i think it's a better approach to have a tight client, that not holds all the hibernate jars and have its own connection to the DB but connects to a server that handles DB-Connections.
I don't really like the Idea (even it seems really proven) to create DTOs to send Objects to the client.

Your client should be working with a RESTful service on the server side... might i suggest Spring-Data-Rest with Hibernate as your ORM?

http://projects.spring.io/spring-data-rest/