Java: Embedding Spring Batch Admin Into An Existing Application
For my current project, I need to share Spring beans between my front-end web servlets and the Spring Batch jobs that I’ll launch from Spring Batch Admin (SBA). This sounds straightforward - configure the SBA servlet to listen on /batch/*, and you should be good to go. However, of course it’s not that easy.
URL Path Mismatch
The first problem you run into is bad links in the menus, form posts that go nowhere, and missing CSS files. This is because SBA expects to be deployed on /, not /batch, or /myapp/batch which is where it will go if you deploy it inside another app. You can survive in this mode for the most part by correcting menu URLs after you click them, or use FireBug to change form actions before you submit them - for example, from /batch/files to /myapp/batch/files, but who wants to live like an animal?
Spring Batch Admin 1.2.1 to the Rescue
Spring Batch Admin version 1.2.1 adds the ability to set the base servlet path for all links and forms by overriding the “resourceService” bean. I’m sure there are several ways to successfully accomplish this, but here’s what worked for me.
Add the following repository:
and the dependencies:
Configure the Batch Admin Servlet - notice contextConfigLocation:
This is the context file that’s only used by SBA. Keep in mind that any beans defined in your root Spring context will also be available to the jobs that are launched by SBA.
One Last Gotcha - /myapp/batch
The main “Home” link in the SBA action bar navigates to /myapp/batch. This doesn’t work the way I’ve wired it up, because the SBA servlet is configured to listen to /myapp/batch/, but not /myapp/batch. I tried adding another servlet-mapping to /batch, but the servlet won’t answer requests to it.
I’m sure there’s a better way to do this via config only - please tell me if you wouldn’t mind, but I opted for the more manual way, just so I could move on.
I wired up a servlet in my main web app to listen to /batch, and then have it redirect to /batch/.
web.xml - configuration for a servlet in my main app
Pay attention to the last servlet-mapping. This gives /myapp/batch over to Spring MVC for URL mapping.
Here’s where I redirect /batch to /batch/. Again, I’m sure there’s a better way to do this (let me know!). Of course, for this specific code to work, you’ll need some dependencies such as spring-webmvc. The bottom line is that I’m just manually listening on /batch and redirecting to /batch/.
Know a Better Way?
Ideally, I’d like to either get Spring Batch Admin to listen to /batch or /myapp/batch, but I’d settle on having a redirect configured in web.xml. Please tell me if you know of a good approach. I moved on with this good-enough solution.