WebSphere, ADMA5006E, and java.lang.NullPointerException

After compiling some code with the Oracle JDK,

java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)

I deployed to WebSphere I got the following error:

ADMA5006E: An error occurred configuring [my application name] in WebSphere Application Server repository: java.lang.NullPointerException

After adjusting my JAVA_HOME to point at the WebSphere Java,

 java version "1.6.0"
Java(TM) SE Runtime Environment (build pwa6460_26sr7fp1ifix-20140220_01(SR7 FP1+
IX90136+IX90137))
IBM J9 VM (build 2.6, JRE 1.6.0 Windows 7 amd64-64 Compressed References 2013123
0_180580 (JIT enabled, AOT enabled)

I was able to deploy to WebSphere.  While the javac command did not specify the target Java version, and the version 1.8 byte code may have problems running on a version 1.6 platform, getting a java.lang.NullPointerException doesn't seem like well-written error handling?

xsi:type and XMLSpy support

As always, something new to learn, even when it is something old!  xsi:type enables overriding the default type of an element with a derived type.  See:

Using xsi:type

Using Derived Types in Instance Documents

Another example of how xsi:type is used, in Health IT:  Combining time intervals in CDA and some more related discussion on combining time measurements.

In terms of Altova XMLSpy support though, my understanding is that with XMLSpy Enterprise Edition 2014, rel. 2 sp1, the Schema tab/view does not indicate that there are derived types available for an element's type, nor does it support switching to view the structure of these derived types.  However the Text tab/view does support auto-completing with any of the derived types once we type xsi:type=

UMLet quick-start guide

UMLet is a simple but effective software design tool.  It compares favorably against heavyweights such as Microsoft Visio.  Some key things to know for the beginner or someone who hasn't used it in awhile:

• To duplicate an element, double-click the element
• Adjust the arrow head or line format by adjusting the text in the Properties pane
• To select, press Ctrl and then mouse-drag around the elements you want

More help and some ideas of what can be done.

Joel Test: Applicability in 2014?

I think the Joel Test is still very applicable in 2014, almost 15 years later.  While organizations should be considering doing more than the list states in its brief yes/no questions, the Joel Test serves as a minimum baseline that organizations cannot dismiss or argue with.  Therefore, I don't believe the Joel Test needs updating. 

However, some worthy, relatively recent elaborations on the Joel Test include:

• The Joel Test – Updated for 2010
• The Joel Test updated for 2013

Being a consultant, I find the Joel Test applicable to new projects I join, rather than applying it to an organization.  When leading a project, it is also a good checklist.

Where do you find WebSphere Application Server port information?

For WAS 8.5.5.2, to find port information, on the left-side of the admin GUI, Servers > Server Types > WebSphere application servers.

Then, on the main part of the GUI, choose your server, then Configuration tab > Communication sub-section > Ports

Notes on "The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)"

• Joel Spolsky's blog post
• Unicode is a "character set", which does not state how it is stored
• Misconception:  That Unicode is simply a 16-bit code where each character takes 16 bits and therefore there are 65,536 possible characters; Unicode is not an encoding
• In Unicode, letters map to "code points", e.g. U+0041 rather than bits, e.g. 0100 0001
• Different fonts display code points differently
• Unicode can define more than 65,536 characters
• In UTF-8, an "encoding" (how string is stored in memory, disk, etc.), every code point from 0-127 is stored in a single byte. Only code points 128 and above are stored using 2, 3, up to 6 bytes.
• UTF-16 stores in two bytes only, not more than 2 bytes
• It does not make sense to have a string without knowing what encoding it uses.  You simply cannot display it correctly or even figure out where it ends

Connecting to Nexus 7 device for debugging on Windows 8.1

While the instructions Using Hardware Devices and OEM USB Drivers are adequate, here's my experience setting up my 2nd generation Nexus 7 on Windows 8.1 Pro.

When connecting the device to my computer's USB port, Windows does recognize it and installs drivers, but treats the device as a Music Player:

At this point, adb does not recognize the device for development purposes:

However, after following the instructions for the Google USB Driver, I get the following: 

and from adb, I do see the device listed when doing the command "adb devices".

Registering device for Windows Phone 8 development

In order for the phone to be registered for development, it also needs to be browse-able in File Explorer when the phone is connected.  In my experience, the most common problem is assuming that any USB cable is compatible when in fact some cables are only useful for charging:  Windows Phone 8 is not detected by your computer

When there are problems you may see the following screens:

When the phone is properly detected, you will see the following:

Upon clicking "Register", if your phone is also connected to the Internet, you will see the following in moments and be able to deploy your applications to the device:

Setting up Apache Cordova/PhoneGap

Based on following the steps in the official PhoneGap documentation, the following document augments that information with more details, specifically around setting up on Windows 8 and for developing Windows Phone 8/Android apps:

Setting up Apache Cordova/PhoneGap (version controlled)