TSSJS: Advanced JPA

http://jroller.com/page/fate?entry=tssjs_advanced_jpa

Sometimes I'm a bit of a glutton for punishment. You'd think that after attending so many conferences, seeing so many JPA drivel talks, I'd stop. Alas, I can't seem to help myself. and am dismayed to find myself sitting in Advanced Topics in JPA by Mark Richards.

It's evident that the use of the word 'advanced' was somewhat liberal in this case. All we've done so far (20 minutes in the talk) is discuss the joys of join tables, entity relationships and how to define them. I shudder to think of what Mark would consider to be an 'intro' talk. Perhaps a 20 minute discussion on the benefits of casting? The benefits of coding with eyes open and thumbs out of anuses, to maximise JPA productivity?

Even more worrying, he actually makes JPA config look so much skankier than it actually is. Switching from hibernate to toplink for example in his case seems to require changing 20 lines of Spring xml. Spring? Yes indeedy, he managed to sneak SpringSpringSpring in there! Either Mark or Spring is pretty fucked up if changing implementations is so much work (it's the former, incidentally).

To his credit, Mark is actually a good speaker, he's just cursed with abysmal material. OHMYGOD, he didn't just.....OHMY...

This is a brave move indeed! Totally unexpected. We were happily traipsing about in many to one land when BOOOM! He brought in...MANY TO MANY! There's an inaudible gasp from the audience at his sheer gumption and audacity. What will this crazy guy do next? Drop his pants and moon us? Masturbate into the first row of attendees? I might explode from excitement and anticipation.

As if that excitement wasn't sufficient, this crazy man just tossed in fetch types. I'm going to need a nap shortly to recover from this.

Oh wait, all is not lost, he actually mentioned something interesting (honest). Throughout the demo, he seems to pointlessly switch from Hibernate to TopLink for no reason, but this finally paid off with showing (what he alleges) a non-compliance by Hibernate, which apparently doesn't support fetching multiple collections, which the spec says must be supported. We switch to TopLink and all is well.

Next we're covering compound keys, which I guess is finally venturing to the realm of potentially non basic trivial features, too little too late I'm afraid. The one thing I am enjoying about this talk through is the hibernate bashing. He's showing fairly standard JPA usage, no custom stuff, yet hibernate seems to shart itself pretty regularly as a result. The latest example is that @IdClass is basically broken (and yes, that's been my experience too). I do like the advice that once hibernate takes a big dump, it'd worth switching providers just to see if it's because hibernate developers are cocksucking chozgobblers, or if it's you who is being a muppet.

Finally, we cover stored procedures, also pretty interesting and I'd say something that does qualify for advanced usage.

All in all, I'm not nearly as angry about this talk as I was in the first 20 minutes. It started off with boilerplate JPA but did eventually manage to eke out some useful info. A speaker who seems interested in his subject and is coherent is such a refreshing change as well, even though he does smirk a lot.