Bug fix: use version numbers instead of JKDLevel identifiers when configuring the MOJO (reported by Loris.)

 - use a static httpserver
 - add new class loader to the static httpserver when a new interface is exported 

 - NodeInput/OutputStream now extends ObjectInput/OutputStream and mainly overrides the annotateClass and resolveClass methods to support the re-generation of node classes.
 - The AbstractNode class now implements Externalizable. The read/writeExternal methods are responsible to read/write node states on streams.

This new implementation allows to resolve a bug in the serialization when a serializable decoration contains a reference to an AST Node.

ast-core : 
 - Fix a bug in NodeInputStream
 - Add support to specify the base node class used by  AST node classes generated by the XMLNodeFactory.

fractal-adl :
 - Fix bug in FractalADLLogManager for the handling of log files.

maven-fractaladl-plugin :
 - Fix integration tests to be compatible with maven 2.1

Removed the CXF patch included into the REST connector.

binding exporter/binder caller instead of the class loader
where Fractal ADL was loaded initially.
This allows us to load a plugin present in the class loader
of the caller but not present in the class loader of Fractal ADL.
This changes nothing for most of simple applications as both
class loaders are the same one, but is required for OW2 FraSCAti.

Additional method in LogLevel.

Bug fix.

The previous implementation was retrieving a Result object which was supposed to report when errors had happened. However it seems that the behavior was somewhat strange and this was not the case (was the object transient?)
Feature reported by Philippe.

In the model of an architecture descriptor with collection interfaces, provide a way for retrieving bindings in the order in which they were registered.
This is needed for example in FraSCAti/Tinfi when the tinfi-emf module (.composite parser) is used with the ultra-merge optimization level source code generator, especially for multiple references (aka collection interfaces): the generator is now guaranteed to retrieve references in the order in which they were declared in the .composite file.

Code cleanup.

Not relevant with the asynchrony due to multi-threading. Would be too tricky to implement and not worth the effort.