Description Chuck Bridgham 2010-05-05 10:21:10 EDT

Recently it was discovered on older workspaces, the component references didn't capture the "archiveName" element, and the method above didn't protect itself in this scenario.

The following exceptions were being thrown because the archive wasn't found  

!ENTRY org.eclipse.wst.common.modulecore 4 0 2010-05-05 10:09:16.078
!MESSAGE 
!STACK 0
java.lang.NullPointerException
	at org.eclipse.wst.common.componentcore.internal.util.VirtualReferenceUtilities.getDefaultArchiveName(VirtualReferenceUtilities.java:71)
	at org.eclipse.wst.common.componentcore.internal.util.VirtualReferenceUtilities.ensureReferencesHaveNames(VirtualReferenceUtilities.java:60)
	at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.customizeCreatedReference(EARVirtualComponent.java:97)
	at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferences(VirtualComponent.java:396)
	at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getHardReferences(EARVirtualComponent.java:86)
	at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getReferences(EARVirtualComponent.java:180)
	at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getReferences(EARVirtualComponent.java:209)
	at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl$GraphUpdateJob$1.run(DependencyGraphImpl.java:352)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at