Ask HN: Java-based integration development learning path

CXF is also good stuff.

I don't know about courses, but given the way I learn, here's what I'd do (and this isn't far from what I did when I first wanted to learn Camel) - figure out some kind of project you can build, that could use Camel, and just start building it.

If you're already building apps using Spring/Grails/etc. then build yourself a simple little CRUD app of some sort... used a totally made up domain if you want (a buddy of mine was making a "Teletubby Tracker" app) and then start thinking about how you might decompose it into a more modular form ("SOA-ify" if you will) and then break the back-end out into services, expose then using CXF, and have your front-end put messages on a Queue, route with Camel, and then update the backend as appropriate. It's fine if it's made up, your goal is to learn, not to build The Next Big Thing, right?

Another piece you might add to the stack at some point is a BPM engine like Activiti.

This approach might or might not be for you (learning styles differ and all that), but "build something" has always worked best for me.

Also, and hopefully without being too self-promotional - if you want to hack on some of this stuff in the setting of a cool open source project, I have some stuff I'm working with that uses Grails, Camel, JMS, (not so much CXF though, at least not at the moment) and Activiti. If you would like to poke at our code and maybe get involved, shoot me an email and I'll try to help out.