An interesting problem that has no universal good solution is: how do I change the configuration of a running Spring application? Spring Batch Admin 1.0.0.M3 was released recently, and it has a configuration upload feature that solves this problem in a particular way. Someone asked for this feature at the recent S2GForum in Munich (if you missed that sign up for events in London and Amsterdam in May), and I was happy to tell him that it already existed, so maybe it deserves a bit more air time…
Screenshots of the Basic Use Case
We start with a look at the Jobs view in the application. It shows a list of jobs that are either launchable or monitorable by the web application.
Now the plan is to upload a new
We press the "Upload" button and the configuration is uploaded and parsed and the
You can see a new entry in the job registry ("test-job") which is launchable in-process because the application has a reference to the
Variant of the Basic Use Case
A common variant of the basic upload use case is to upload a modification of an existing
How Does it Work?
The secret to the implementation of this use case is that
Visit the Batch Admin website for more information and to find out where to get the code to play with. Remember the S2GForum events coming up in London and Amsterdam in May, where the application will be discussed and demo-ed in a session by the Spring Batch and the Spring Integration leads (Dave Syer and Mark Fisher).
- Introducing Spring Batch Admin
- Running a Spring Batch Job in The SpringSource Application Platform
- Practical Use of Spring Batch and Spring Integration
- Uploading to Amazon S3 using a custom ANT task
- Using Cloud Foundry from STS