Dear loyal readers (both of you),
I’m contemplating a Hibernate upgrade. Does anyone have experience with doing a major Hibernate upgrade? And by “Major” I mean I’m going from 3.3.1 to 3.5.3. That’s about 2 years worth of upgrades I’m going to try and implement.
Does anyone know of any issues with that?
Speaking of which, this is exactly the type of topic I want to discuss in this forum. We’re all interested in Java, and enterprise application architecture. And these types of issues come up all the time when we’re dealing with EAA. Once an application hits production, our work is just beginning as architects. We owe it to our employers (or in my case, my customers) to have a plan to safely shepherd their applications through their useful lifecycles with a minimum of problems. Don’t we?
I’d love to hear from you. And thanks for reading!
I’ll tell you why! For one, you can participate in a new Group called Java Enterprise Open Source Application Architecture.
Go to My Developer Works and click on the Register link to sign up. It just takes a minute and then you can participate in that group and thousands of others, and read my blog (I know you’ll want to do that).
Have fun. Thanks for reading!
And I’m not just saying that because they’re mine. Okay, before I get too weird here (too late?), I should explain. I learned while re-writing the Intro to Java Tutorials, Part I and Part II for IBM Developer Works that the term for “tutorial” is “toot”. Seriously. I thought that was pretty cool. But being an old school Beavis and Butthead fan (well, really a Mike Judge fan), I went right to farts.
I’m really just lettin’ ya know that there are two new Java Toots, er, Tutorials out there. Check ’em out, and let me know what you think.
And if you think they stink, well, I guess that’s your call.