I don't know how many hundreds of hours I have wasted with fiddly configuration stuff like this. You'd think that nobody would be stupid enough to make errors such as compiling the WAR with the wrong version of Java, but you'd be wrong. Now why could that information not be prominently displayed in the web page? Or at least in the logs? Dear reader, if you work on developing tools for developers, please put every irregularity in their face. Numbers, which are greater than those found in the Java Runtime Environment version 1.7.0_40.
: Class Initializer has unsupported major or minor version Remote failure: Error occurred during deployment: Exception while loading the app : “The requested resource is not available”įinally, instead of using autodeploy, I logged into the server and deployed manually: $ asadmin deploy codecheck.war The app ran on my machine and not on the server. [[Attempt to create file /opt/domains/domain1/autodeploy/.autodeploystatus/codecheck.war failed įor an hour I tried This And That, to no avail. Instead of noisily squawking about what ails its innards, it had turned into the strong and silent type: Why can't GlassFish be like Play or Rails, and give the file name and line number of the offending artifact?īut there is something worse than the Stack Trace from Hell. Now if there is one thing that I really hate in life it is the Stack Trace from Hell. Ugh, not again! Time to check out the logs. Being a conscientious (and slightly pessimistic) person, I pointed my browser to the server, and whoa: It worked locally, and I ran the script to upload the WAR. So, this morning, I made a small fix to my side-project, the code-check autograder. Or, if you'd rather learn from a book than a list of links, you know what to do.Īs my wife knows, if there is one person who can wring a drop of unhappiness from even the happiest event, that's me. It's a major release-the biggest change in the Java language since Java 1.0 and the biggest change in the Java API since Java 1.2 (Or was that Java 2? Or Java 2 version 1.2?) Here is a great list of links.
I don't think I add any value by writing my own. These days, the blogosphere is awash in blogs that sing the praises of Java 8. That's the nice thing about backwards compatibility. Eclipse came up fine, and my Scala-based tools for e-book production worked without a hitch, and I forgot all about it. Now I downloaded the official release and changed JAVA_HOME and the PATH one last time.
But I switched JAVA_HOME and the PATH whenever I worked on the book. Of course, I have used it for about a year, while writing my book Java SE 8 for the Really Impatient. Just make sure you don't get tripped up by the change in the classfile format!Īfter all these years, Java 8 is finally available. Hello Java 8 (and how it makes GlassFish speechless.) Hello Java 8 (and how it makes GlassFish speechless.) After all these years, Java 8 is finally available.
0 kommentar(er)
