Some time ago we started to create our own intranet called CoffeeNet, which is a microservice landscape based on our own Spring Boot Starters, a service discovery and an OAuth2 service. The vision is to create a system with a very easy integration of new applications by just adding a few Spring Boot Starters and starting to code the specific functionality of the new service.
Tag Archives: spring
Recently we had a problem related Springs auto-proxy feature that I think is worth writing about.
We use Spring as our framework of choice because it provides us with a nice set of convenience features when bootstrapping and plugging together our application.
One of these features is caching: We cache our users' roles because their definitions are stored in a pretty slow external system and change rarely.
This is the second article of a springboot & reactjs article series about server side rendering and progressive enhancement. In the first article we have learned how to render a ReactJS app on the server with nashorn. However, actually it is not really an "app" yet. Currently we just see a static list of awesome products...
springboot & reactjs article series
- server side rendering ✅
So that's it. Three days, 2.000 Developers from 20 countries, over 140 speakers from around the world, and one outstanding beautiful city. It is for the first time, when Devoxx Poland (previously known as 33rd Degree), one of the most recognizable European Java Conference took place in Krakow, the city of the polish kings, and one of the most important places in whole polish history. It took place from Monday to Wednesday last week in the ICE Conference Center, which is located directly by the Vistula river, with beautiful view over the Wawel Royal Castle.
There are a number of reasons to use the Spock testing framework:
First, tests - specifications in Spock speak - written in Spock are well structured, expressive and therefore provide good readability. In addition, Spock has built-in features like data driven testing and interaction based testing (mocking). Data driven testing allows your test code to be reused, i.e. to be applied multiple times with different parameters.
My team and I are currently working on an project we first started in early 2010. The application is in production since sometime late 2010 and there has been no active development except for minor enhancements and bugfixes since then. Even if our code, processes and tools were good in 2010 we've improved a lot since then. Working on my old projects is one of the occasions, where this becomes most evident.
You want to execute cron jobs or call your methods asynchronously? Thanks to Spring's annotation support for scheduling and asynchronous execution you can achieve this in a few minutes.
Some xml magic
At first define your task executor and scheduler. The following lines will create an instance of ThreadPoolTaskExecutor and an instance of ThreadPoolTaskScheduler with the given pool sizes. The task element annotation-driven allows you to use Spring's annotations for scheduling and asynchronous execution within the beans defined in your application context.
JMX (Java Management Extensions) provides the infrastructure to support monitoring and management of your Java applications. Resources you manage with JMX are called Managed Beans (MBeans). I want to show you how to quickly register your own Service as MBean using Spring and Source-Level Metadata (JDK 5.0+ annotations).
A while ago we wanted to store internationalisation for a project in database to allow (a subset of) users to create and update internationalisation using the application itself. When we searched the web for existing projects that allow to do this we did not find a good and ready to use solution. This is why we decided to write the code ourselves and make it available to others, especially since there was some public demand and it will probably not be shipped by SpringSource (check out Google for details).