3 comments on “Getting started with ReactJS, Play 2.4.x, Scala, Anorm and WebJars”

Getting started with ReactJS, Play 2.4.x, Scala, Anorm and WebJars


playing-reactjs This blog describes a basic example to render UI using React(A JavaScript library for building user interfaces) with Play 2.4.x, Scala, Anorm and WebJars. It also demonstrates the use of evolution in Play 2.4.x This is a classic CRUD…

2 comments on “Play Framework 2.2 with WebJars client-side web libraries”

Play Framework 2.2 with WebJars client-side web libraries


WebJars are client-side web libraries (e.g. jQuery & Bootstrap) packaged into JAR (Java Archive) files. WebJars can be added as dependencies to an app by simply adding them to the build.sbt file. There is also a helper library named webjars-play…

0 comments on “Employee-Self-Service: Reactive and Non-Blocking Database Access using Play Framework and Anorm – (Part-4)”

Employee-Self-Service: Reactive and Non-Blocking Database Access using Play Framework and Anorm – (Part-4)


Last week, We have added Database Access as Reactive and Non-Blocking behaviour in Employee-Self-Service  application. Now we have added some more features. These are following: Achieving, Futures to use more idiomatic error handling. Replaced the embedded JS & CSS libraries with WebJars. Achieving,…

2 comments on “Preparing Seed Data for Your Application on Google App Engine”

Preparing Seed Data for Your Application on Google App Engine


For the past few weeks, we have been getting requests on our website about the way we generated seed data for our multi-tenant application. I thought it would be best to talk about the method that we used as a…

7 comments on “Multitenancy in Google App Engine: Scope of NamespaceManager”

Multitenancy in Google App Engine: Scope of NamespaceManager


As you would have read in our previous post, we used the Namespace API to make the SaaS application that we were working on multi-tenant in a matter of four hours. You would have noticed that we set the tenant…

4 comments on “Managing Multiple Parent Persistence Problem in App Engine”

Managing Multiple Parent Persistence Problem in App Engine


We are in process of porting an entire application on google app engine. This application has persistence using JPA and as usual contains mapping between entities using annotations. The mapping like @OnetoMany and @ManytoOne in Jpa may throw lot of…

8 comments on “Why Unowned Relationships Make More Sense With App Engine Datastore”

Why Unowned Relationships Make More Sense With App Engine Datastore


A month back we started migrating an enterprise time keeping and invoicing system to GAE. Initially, the application was deployed at the enterprise on tomcat. The opportunity was to port the application to GAE and utilize the public cloud space.…