when writing out file to disk.

fragment was surrounded by an <Xdmf> tag.

The bug appears when trying to use a filename given as:
file:///path/to/xmf/file.xmf and the xmf contains a reference to an h5 file.

- When writing you will end up with a file called 'file:' which contains
random data.
- When reading, libxml2 has no problem opening the xml file however
getRealPath() returns the wrong path for the h5 file. If you try to
use file.xmf from the to directory (ie: read("to/xmf/file.xmf")) the
h5 file will be loaded from 'to/file.h5'.

To correct the issue, we strip out the unwanted scheme and other stuff
in the URI and just use the path. (libxml has functions for this)

Additional xmf files are now read in via href'd xincludes which broke
mapping of xmlNodePtrs to XdmfItems (which qas necessary to enable shared
pointer representation in file).  This mapping was fixed.

XdmfCoreReader.cpp had a bug that resulted in an infinite loop when
resolving xincludes. This bug was fixed. Added ability for xincludes
to resolve href links (links to other files).

Fixed formatting in XdmfWriter.cpp

Unpartition method takes an XdmfGridCollection of unstructured grids
and zips them back together into a single XdmfUnstructuredGrid. It uses
GlobalNodeIds to perform the unpartitioning.

Also added some functionality to the partitioner so that it will properly
partition set attributes of types other than scalar.

XdmfTopologyType.

The new version of metis uses a different format to supply connectivity
information to the partitioning algorithm. The new format allows generic
element types to be passed (as well as mixed topology formats). These changes
expand the number of element types we can partition in metis (this was tested
on high-order hexahedron, linear hexahedron, and polyline topologies)

Fixed Java Loading issue. You no longer need to use static { System.loadLibrary() } at the begining of java code

node connectivity has been changed.

Modify XdmfTopologyConverter and XdmfPartitioner to work with new
topology types.

This looks like a bug in swig since the fix is not proper C++
Surrounded by a ifdef swig block. If anyone has a better fix for this
I'd like to use - this is a hack.

around to prevent compiler warnings.

to the libraries.