Skip to main content

Java won the language wars

It seems that almost all of Enterprise development work these days and for the past 10 years or so is done in Java. Specifically done in the Java Enterprise Edition. Previously, I avoided the Enterprise Java world, I preferred desktop Java everything related to J2SE.  J2EE appears to be very complex though and takes a while to learn, I'm only taking my first steps now.

Java knowledge opens up quite a few career avenues. J2EE leads to Enterprise development roles where the projects can be small and nimble or large and scalable. JSP and Servlets lead you to learn a lot more about HTML and Web technologies whilst still using your Java skills. You could also learn the Goolgle Web Toolkit GWT which is developed in Java.

The Android ecosystem allows Java developers to create amazing applications for phones & tablets.

It's an exciting time to be a Java developer.

Popular posts from this blog

Overcome Java JNI gdb errors on GNU/Linux

If you happen to try to debug any Java JNI programs using gdb on GNU/Linux you will soon come across error messages. For example : $ gdb --args java MyJavaProgramUsingJNI cannot find user-level thread for LWP nnn: generic error warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match The reason for this is that the java program mucks around with LD_LIBRARY_PATH and that prevents gdb from running correctly. To overcome this, you have to run your Java program and place a pause in the Java code, such as reading a key, and then in another shell, run gdb to attach to the running Java process. You can then set your breakpoint on your JNI code and debug it. Here is an example : Compile your Java program: $ javac JNITest.java Generate the JNI header file: $ javah -jni JNITest.java Create and compile your C code library: $ cat jnilib.c #include "JNITest.h" JNIEXPORT jint JNICALL Java_JNITest_addValues( JNIEnv...
Read more