javadoc.exe man page

http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html

Generating Javadoc using MyEclipse

It seems that some versions of MyEclipse don't have the "Generate Javadoc..." option under the main Project menu that "regular" Eclipse does, at least MyEclipse 7.5. The facility for generating Javadoc is still somewhere; one workaround way to access it is by opening the help menu, searching for "javadoc" and opening the second result, "Javadoc Generation." That help file has a link to the Javadoc Generation wizard.

soapUI is powerful

soapUI (on SO) has its own API of built-in methods. It allows for scripting in Groovy.

Bonus link: soapUI tips and tricks, including a runTestStepByName-esque method.

Intro to Groovy

http://www.javalobby.org/articles/groovy-intro1/

Setting Eclipse diff tool to ignore whitespace

Open Window > Preferences from the menu bar
Select General > Compare/Patch in the left-side tree menu
Check "Ignore white space"
Press Apply, then OK

(from http://masa-paris.spaces.live.com/Blog/cns!F61AACB5DACD22A7!884.entry)

XML targetNamespace

"When we want to [validate an XML doc], we need to identify which element and attribute declarations and type definitions in the schemas should be used to check which elements and attributes in the instance document. The target namespace plays an important role in the identification process."

-from w3c here

Qualified and qualified elements are discussed on this page under the section "Qualified or Unqualified."

Qualified: "all the elements and attributes in the instance must have a namespace, which ... adds namespace complexity"
Unqualified: "only the globally declared elements and attributes in the instance must have a namespace, which ... hides the namespace complexity from the instance"

The meaning of global is described on this page:

"When an element declaration is a child of the xs:schema element, the declared element is global. Global elements can be referenced by other element declarations, allowing for element reuse."

More on global vs. local here.

Validating XML against schemas in Java

XML validation with namespaces will not work properly unless the DocumentBuilderFactory has namespace awareness turned on manually, via setNamespaceAware.