Adding functionality for examples.

Examples are now coded in doc as

"examples" : [
    {
        "param1" : "value1",
        "paramN" : "valueN
    }
]

within the method object. The keys in examples must be equal to a
parameter name.
"Adding method toJSString that allows converting Freemarker types to string"
Support for optional parameters discriminated in console.

Optional parameters are now declared inside request as:

"optParameters" : [
    { "name" : "paramName" , "description" : "paramDesc" },
    ...
]

* Vectorized values are not yet supported.
* Whether the parameters is passed through query string or not still
depends ond weather it appears on the URI.
* Utils have method to convert FreeMarker value to js readable format
Corrected: +- sign changes without modifing header. Console collapsables
work.
Created detail.js to manage most of detail.ftl js file.

Could not get detail.js to manage code which used freemarker directives.
Added tabbed consoles with post functionality.

Codemirror files added for json post console.
jquery and tabs css files added for tabbed consoles

In doc:
    *"examples" now supports "postFile" which is the url relative to
    'resources' of the text file with the json related to the example.
    *"examples" parameters for GET method are now within "getParams"
    object.
    *Method object now uses "supportedMappings", a list of string to
    define which mappings it supports. No definition of the attribute
    means "GET".
    *POST url is defined in "postMapping" attribute
Changes to mantain retrocompatibility
Moved some path definitions to paths.ftl in order to access them
everywhere. Post now show the result in a new console.

Post result code should be reviewed so it shows more information.
Json schema document that partially documents the 'doc' file structure
Parametrization of 'resourcesPath' for the post example code.
ResourcesPath is defined in paths.ftl. Documentation is almost complete.
Added ifs for types definitions. Changed filters id to 'filters'.
Finished documentation of current usage.
Multiple mappings for a simple method is now properly implemented with
retrocompatibility.

The 'method' attribute in a method can now be an object like the
following:

{
    "get" : "get URI",
    "put" : "put URI",
    "pull" : "pull URI",
    "delete" : "delete URI"
}

At least one of these must be defined. The keys in this object defines
which mappings are supported by the method. The value URI is the URI to
which the http is requested.

To mantain compatibility, method can still be a string, and
requestMapping must have the URI. Otherwise, requestMapping is ignored.

supportedMappings and postMapping are depricated and no longer
supported.

Work is left to be done on which URI is used to shown in the index page.
Small changes in doc.json
Review of comments in index.ftl and detail.ftl.
First not correct implementation of "open in new window" for consoles.
Added new tab post for POST console.

Requiered a dummy get method in DocumentationController that returns an
empty json to be overwritten.
When defining multiple mappings using method : { "get" : ... , "post" :
..., etc. }, it is not certain which mapping to show in the index page.
It can be selected now via the "preferredMethod" attribute.
Support for shortName
Now children parameters are shown in console.