1 shitty container + 1 shitty persistence framework = ???

Of course, a cakeful of shitty applications. This is a funny experience, well I consider this funny so let me consider this two shitty things as the two stooges chasing a gopher but eventually hitting each others head in the process. I tried to run a sample application using Hibernate 3 on Weblogic 8.1, Hibernate is using ANTLR for some reasons maybe to process it's HQL dynamically, whatever that means. There is some sort of a query factory class that H3 has started using and for some reasons it causes a CharScanner.panic() in the ANTLR which by default will shutdown the JVM. I don't have anything against ANTLR, that is a very good tool written by a very good programmer who deserves to be really in "front of the keyboard", not these goofy jerks from Hibernate and Weblogic.

So here it is, I encountered this panic() that is configured normally as per instructions, believe it or not it actually shutsdown the Weblogic Server! Weblogic, by default, allows itself to be shutdown!!! Of course some goofy there will tell me, "you should modify the policy file" yeah you're right as if they're really going to do that if this pest didn't bite them. And I tried replicating the same error on Sun Java System Application Server PE 8.1 and it disallowed the process without me having to tweak anything for the first time. Imagine of you have several 24/7 applications sitting on the server, that is nightmare!

14 Marines just died recently in Iraq, it may be more if these two shitty products are running some show over there.