Skip to main content

Spring Data very simple example with Postgres

Hi Folks

Today it's again about server technologies and data persistence, but with spring-data project. This project aims to eliminate boilerplate code required to create the data tier, and not only that,

it also eliminate the code required by ORMs like hibernate to manage session and entity manager and everything we used to do to persist our data. enough talking.

technologies used :
a- spring data
b- spring mvc for simple rest api
c- hibernate as JPA provider
d- gradle for build management
e- ide of your preference, I used intellj in this one.
d- postgres as db

 1- Business as usual we need a simple project structure, I'll keep it simple but scalable :


spring-data-sample (contains gradle root stuff: build, settings)
------ bl : data and business tier, merged together as we don't have any code for data!
------ web : where we expose bl with rest apis

 2- setup the database, and by that you only need to install postgres and prepare the database, I created one called 'cars'. hibernate will fill it for us.

3- Business layer

in build.gradle you need these dependencies :
dependencies { compile '' compile 'org.hibernate:hibernate-entitymanager:4.2.6.Final' compile 'org.postgresql:postgresql:9.4-1200-jdbc4' }
and for the configuration :
annotations :
@EnableJpaRepositories : scans where our repositories are (i'll get to define what a repository is)
@EnableTransactionManagement: allows you to use @Transactional,

a- data source : db connection
b- entity manager factory : for ORM to work, scans entities and defines hibernate properties
responsible for managing sessions and entities and all that ORM stuff.
d- transaction manager
and for our entity, nothing new, just a simple pojo with persistence annotations

now the fun part, all you have to do to get default crud operations is this:

out of the box you will get the following:
1- save (create & update)
2- delete
3- find, findAll, findByColumnXAndColumnY...etc
and to use it we have CarBo as a BL bean :
and the rest is the web part I'll leave it to you to check in the repository. Good Luck !


Popular posts from this blog

Spring 4 + Hibernate 4 / Java configuration / rest service example with gradle

In this post I'll explain the required work to create a rest API utilizing both spring and hibernate version 4, and the configuration will be using java configuration classes not XML. I'll use gradle to build and for dependency management, it's way easier than maven and keeps you focused on the application, if you are not familiar with gradle and interested in it see my previous post about it. The first part which is dependency management is covered in gradle post mentioned above. I'll skip to explain each tier of the project and its configurations: As you can see we have 4 tiers: 1) DAO tier / data tier In this tier we configure the datasource and hibernate, I used HSQL in memory db it can be easily substituted with other db engine providing the right dependencies The DaoConfig defines the data source, transaction manager, session factory and  hibernate properties The most important part is the annotations : 1)  @Configuration  : to tell spring th

Android RecyclerView - Adding Empty View

So RecyclerView was introduced to replace List view and it's optimized to reuse existing views and so it's faster and more efficient as stated in the documentation: While using it, I faced the issue of missing a useful functionality that is implemented in ListView. that feature is setting an empty view in case there was no records. In ListView it was as simple as this View emptyView = findViewById(; ListView  myList = .... myList.setEmptyView(emptyView); but this method doesn't exist for recycler view so we need a work around until android team fixes this. and here are the screen shots of both list view and recycler view fix List view : Recycler view : here is how I fixed it: here is the content of empty_view, it can be anything. Enjoy.

[PART 5] NuTracker ReactJS app - Add Login & Profile using Router

In the previous part we finished the dashboard read functionality, now we want to add the skeleton for other pages: - Login   In this page the user will be able to login to their account and the dashboard won't show unless the user is logged in. - Profile In this page the user will be able to update their daily nutrition goals that they can track in the dashboard. to be able to have multiple 'pages' in react and navigate from one to one, we need something that can switch the rendered content based on what we want, we can do that with if statements in the App components and store some location state, but why invent the wheel. React Router every major single page app web framework has the routing concept and functionality to interact with the usual browser urls and switch the content based what user should see. for example on the profile page I want the url path to be /profile, and for login to be /login and so on. in more advanced cases you want the users