Can now specifiy form name

If you create you forms using FormFactoryInterface::createNamed, then you should now be able to tell the ApiDocBundle the correct form prefix.
Merge pull request #255 from adrienbrault/form-type-name

Can now specifiy form name
Adding possibilty to name resource
Adding test for named resource
more readable
Merge pull request #258 from fdubost/master

Allow to named resources
Option to set requirements and parameters directly from ApiDoc annotation

Sometimes required parameters are not used through routing but still they are mandatory. I wanted to have API with

resource.json?foo=bar&something=else

format, that was possible through QueryParam annotation or requirements in routing BUT!

There was no way to set dataType or description

This PR solves problem for me.

Side note: if you want to declare e.g. _format requirement through Annotation or any other param that is used in url ({foo} format) then it won't work. Because Bundle still overrides requirements and parameters after the constuctor in ApiDoc is called. This might be solved in separate PR by adding check if given requirements or parameters was already defined.
Merge pull request #218 from konradpodgorski/feature/extendedAnnotation

Option to set requirements and parameters directly from ApiDoc annotation
Type hint was removed for symfony 2.1 compatibility
more method checks for Symfony2.1 compatibility
fix for php 5.4 compatibility
DI powered approach for symfony2.1 BC
fixing typos in comments
minor code cleanup
cleaner true-false check
ValidationParserLegacy now extends ValidationParser to avoid code duplication
redundant interfaces were removed
coding standards fixing
Merge branch 'master' of https://github.com/restyler/NelmioApiDocBundle